Duve is thrilled to announce our latest integration with Hub OS, a leading task management platform designed for the hospitality industry. This integration leverages DuveConnect to automate operational tasks and services, ensuring seamless communication between Duve and Hub OS. With this new integration, hosts and hotel managers can streamline their workflow, automatically logging guest requests as actionable tasks in Hub OS without any manual intervention.
Overview
By integrating Duve with Hub OS, hotels can ensure that guest service requests—such as housekeeping, room amenities, or maintenance—are efficiently communicated to their operational team. Using DuveConnect’s outgoing webhooks, this integration creates, tracks, and confirms tasks based on triggers from Duve, allowing hosts to deliver exceptional guest experiences with minimal effort.
In order to open Hub OS integration, customers must purchase the DuveConnect Add-on. DuveConnect is an add-on feature that will be available upon request and at an additional monthly cost of $0.50 per unit with a monthly minimum of 50 eur required. For more information contact our Support Team or your dedicated Customer Success Manager.
How It Works
The integration uses unique identifiers and webhooks to map tasks between Duve and Hub OS. The workflow includes:
- Custom upsell Setup: Hosts define free upsells - custom services in Duve (e.g., towel service or deep cleaning).
- Custom Service Setup: Hosts define external IDs for each custom service in Duve (e.g., towel service - 200 or room cleaning - 100).
- Trigger Configuration: Hosts set up triggers in DuveConnect webhooks to send data to Hub OS whenever a guest requests a custom service.
- Task Mapping: Task attributes such as room number, guest name, service type, and delivery time are mapped to corresponding fields in Hub OS.
- Task Confirmation: Hub OS confirms task creation, which is logged in Duve for transparency.
Pricing
The Hub OS integration is available as an add-on at DuveConnect pricing. To enable this feature, contact your Customer Success Manager or Duve's Support Team.
How to set it up:
Prepare Custom Services
- Navigate to the upsells Custom Services section in Duve.
- Add or edit upsells, assigning each item a unique External ID (e.g., Towel Service = 200, Room Cleaning = 100).
Configure DuveConnect Triggers
- Go to Settings > Connections > DuveConnect.
- Create a new connection for Hub OS and add a webhook.
- Select Custom Services as the trigger type and include relevant data points (e.g., room number, guest name, service type).
Set Up Authentication
- Add hotel-specific credentials in the webhook's custom header, including:
- ID: Hotel system identifier.
- Access Token and Password Token: Provided by Hub OS.
Host workflow:
- Create free custom services
- Add an external ID (single or multiple products) on the custom service page
Single item:
Multiple items:
Host go to settings > connections > Duve connect > Add new:
- Create a trigger:
- When the order status is created
- And order type is custom service - the wanted custom service
- Add the Hub OS endpoint
- Add a Custom Header
- When the order status is created
Data Points That Are a Must
To ensure successful execution, the following data points must be included in the webhook payload:
- Order Details: Information about the requested task or service.
- Product Details: Specifics about the service or item associated with the order.
- Verified First Name: The guest's verified first name.
- Verified Last Name: The guest's verified last name.
- External ID: Unique identifier for mapping the request to the external system.
- Room Number: The associated room number for the task or service.
Common Errors and Their Causes
1. Invalid Credentials
- Response Code: 400
- Error Message:
"Invalid credentials." - Error Code:
WEB_HUK_INVALID_CREDS - Cause: Incorrect authentication details in the request header, such as the Access Token or Password Token.
2. Missing Data in the Request
- Response Code: 403
- Error Message:
"Please provide the proper Room Number, External Id, and Verified First Name." - Error Code:
WEB_HUK_INVALID_BODY - Cause: Required data points are missing in the webhook payload.
3. Invalid Request Data
- Response Code: 400
- Error Message:
"Unknown room" - Error Code:
WEB_HUK_HUBOS_REQUEST_FAIL - Cause: The provided room number is not recognized or does not exist in the external system.
4. Request Failed After Multiple Attempts
- Response Code: 403
- Error Message:
"Operation failed after <retryCounter> attempt, Please check credentials and request body." - Error Code:
WEB_HUK_REQUEST_ATTEMPT_FAILED - Cause: The request was retried multiple times but failed due to persistent issues like invalid credentials or incorrect data.
Comments
0 comments
Please sign in to leave a comment.