Booking.com Connection Flow
Purpose
The Booking.com connection feature allows Operations to connect properties to Booking.com through Channex (a channel manager). This enables properties to receive bookings from Booking.com and manage their availability across multiple channels.
Prerequisites
Before connecting to Booking.com, the property must have:
Channex connection established (usually through Airbnb connection first)
Property already listed on Booking.com with an active account
Booking.com property ID (obtained from the Booking.com extranet)
User Flow (Operations)
Follow Booking.com Setup Guide
The modal provides a step-by-step guide:
Channel Mapping
After successfully connecting to Booking.com, the system performs an initial automatic mapping of rooms and rate plans.
Carefully review and finalize this mapping to ensure Booking.com rooms and rates align with those in Hububb.
Once the connection is complete, the user is redirected to the Channel Mapping screen to confirm or adjust mappings.
Next required action: click the "Load Future Reservations" button to pull upcoming reservations from Booking.com into Hububb.
The Load Future Reservations button must only be clicked after the room and rate plan mapping is fully verified and completed. Triggering this step too early can result in reservations being linked to the wrong room, incorrect rate plan, or no room at all, causing data inconsistencies that are difficult to fix later.
System Flow (Behind the Scenes)
Data Validation
Checks if property has existing Channex connection
Validates Booking.com property ID format
Ensures property is properly configured in Channex
Connection Process
API Call: [[#
POST /api/integrations/booking/connect]]Sends property ID, Booking.com hotel ID, and payment method
Creates connection between Channex and Booking.com
Email Notification:
Sends "bdc-listing-live" template email to landlord confirming successful connection
Data Updates:
Updates property's connection requests status to "Completed"
Creates new property channel record
Updates user subscription and invoice data
Navigation:
Redirects to property's channels tab
Opens channel settings if channel ID is available
Backend Flow (What Happens Behind the Scenes)
POST /api/integrations/booking/connect
When an Operations user initiates a Booking.com connection from the dashboard, several automated steps run in the background to make sure the connection is valid, the property is set up correctly in Channex, and everything is stored properly in Hububb’s system.
1. Property & Data Checks
Confirms that the property exists in the database and has rooms and rate plans set up. Booking.com requires at least one room and one rate plan.
If missing, the connection stops and an error is shown.
2. Connection Test with Booking.com
Hububb contacts Booking.com (via Channex) to test the connection using the hotel ID entered by the Operations user.
If the test fails, the process ends and the user is notified to double-check the property ID.
If the test succeeds, the process continues automatically.
3. Service Validation & Subscription
The system determines whether the Booking.com connection service is free or paid based on the landlord’s account.
If payment is required, the subscription is created at this stage. (For manual connections from Property Requests, no payment ID is usually passed, so this part is skipped.)
4. Mapping & Channel Creation in Channex
The system retrieves the property’s room and rate mapping details from Booking.com via Channex.
Hububb automatically builds a new Booking.com channel in Channex:
Linking Booking.com rooms and rates to the property in Channex
Assigning them to the correct property structure
Marking the channel as active
This pre-fills most data for the Channel Mapping screen.
5. Storing Channel in Hububb
A new Property Channel record is created linking the property to Booking.com.
The channel is marked as active.
Room and rate mappings are stored to keep track of the OTA’s structure.
Pending Booking.com connection requests are updated to “Completed” automatically.
6. Notifications
Landlord receives an automatic confirmation email letting them know their property is now live on Booking.com.
Operations user is redirected to the property’s Channels tab with the new Booking.com connection visible.
If any error occurs during the process (e.g., failed mapping, invalid property ID, or missing data), the system updates the request status to “Rejected” and stops the flow so the Operations user can correct the issue and try again.
Important Rules and Edge Cases
Success Indicators
Connection request status changes to "Completed"
Property channel shows as "Active"
Landlord receives confirmation email
Property appears in channels tab with Booking.com connection
Room mapping and rate plans are synchronized