Hub OS Integration – Duve

Duve is thrilled to announce our latest integration with Hub OS, a leading task management platform designed for the hospitality industry. 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 webhooks, this integration creates, tracks, and confirms tasks based on triggers from Duve, allowing hosts to deliver exceptional guest experiences with minimal effort.

Pricing

In order to open Hub OS integration, customers must purchase the Add-on. Hub OS 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 (see below).
Trigger Configuration: Hosts set up 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.

How to set it up?

How to Setup HubOS via DuveConnect - Click Below for Step by Step Instructions

Setup Custom Service Upsells

Go to Upsells > Manage and click '+New Upsell' and select 'Custom'

Go to 'Pricing & Cancellation Policy' and select 'Free' upsells

Note: Only Free Upsells are supported to sync to the Hub OS integration.

For Single Products, add the External ID in the field

For Multiple Items, click on each item to add the External ID

External ID for Each Type of Service

ID	Task Name
2	Change bed sheets
3	Request cleaning
4	Serve towels
5	Check minibar
6	Serve pillows
7	Serve amenities
8	Install baby cot
9	Install extra bed
10	Deep cleaning
11	Taps purge
12	Turndown service
13	Other task
14	Zip beds
15	Separate beds
16	Room service tray
17	Check
18	Review
19	Ventilate
20	Minibar restocking
21	Bellboy
22	Luggage
23	Ice bucket
24	Laundry
25	Valet
26	Securit

Configure Triggers

Go to Settings > Connections > Outgoing > +Add New Webhook

Set the trigger:

When the order status is created
And order type is custom service > Select the Service from the list

Set Up Authentication

Endpoint URL: Request from Duve Support Team
- Add Custom Headers, which will be provided by Hub OS:
  - custom_hotel_id: The hotel system identifier.
  - custom_access_token
  - custom_password_token

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.
First Name: The guest's first name.
Last Name: The guest's 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.

Done!

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.

Hub OS

Browser

App