Cloudbeds

• Live Cloudbeds PMS API
• Rates and availability carousel
• Cloudbeds booking engine deep link
• Reservation lookup (OTA ID or confirmation number)
• Add-ons
• Outbound guest journeys (WhatsApp, SMS, email)
• No invoices, no guest portal

Cloudbeds is a cloud PMS used by independent hotels and growing groups. D3x treats it as the system of record for the stay: agents read inventory and reservations from Cloudbeds, answer with live context, attach add-ons, and run outbound guest journeys on WhatsApp, SMS, and email, with the same Skills Engine and audit trail as every other channel.

This page is the operator view of the Cloudbeds connector. For the marketing overview, see the Cloudbeds integration page. Two capabilities are out of scope here: invoices, and guest portal / online check-in. Cloudbeds does not provide a guest portal, and D3x does not redeliver or modify invoices on this connector.

Rates, availability, and booking

When a guest asks about booking a stay, D3x connects to Cloudbeds and pulls the catalogue the agent needs to answer with live inventory, not a static brochure.

• Room types: the sellable units configured in Cloudbeds
• Rates and rate plans: live prices for the dates and occupancy the guest specified
• Availability: remaining inventory for those dates

That data is used to serve rates and availability in the conversation. Matching room types appear in a carousel: each card shows the room, estimated prices, and a Book now action. Book now is a deep link into the Cloudbeds booking engine, so the guest completes the booking in Cloudbeds with the search already filled in.

1. 1

   Guest asks about dates or a stay

   Occupancy and date range are confirmed in the thread (for example 2 adults, 10 to 14 October).

2. 2

   D3x queries Cloudbeds

   Room types, rates, rate plans, and availability are pulled from Cloudbeds for that search.

3. 3

   Carousel and Cloudbeds deep link

   Available options render as cards with estimated prices. Book now opens the Cloudbeds booking engine for that stay.

Find a reservation

Once the guest is talking about an existing stay, D3x needs the right Cloudbeds reservation in context (past, upcoming, or in progress) so it knows whether they are in-house, not yet arrived, or recently checked out.

Answer questions about the reservation

With the reservation loaded, the agent can answer questions about that stay using live Cloudbeds data: dates, room type, rate, status, arrival expectations, and other fields on the booking. Replies stay grounded in the reservation in context, not generic FAQ copy.

Act on the reservation: add-ons

Beyond answers, D3x can attach extras to the Cloudbeds reservation while the guest stays on the same channel. For breakfast, parking, early check-in, late checkout, and other Cloudbeds products, D3x searches available add-ons for that stay, quotes the live price, and when the guest confirms, attaches the add-on to the reservation.

• Search available Cloudbeds products and add-ons for the stay
• Check the price of the add-on in Cloudbeds
• Attach the add-on to the reservation after guest confirmation

Invoices are not supported

D3x cannot fetch, redeliver, or modify invoices on Cloudbeds. If a guest asks for an invoice, the agent should not promise a document from this connector. Compare with Mews (fetch and send), Opera (Opera emails the invoice), and Apaleo (modify, then send).

Guest portal and online check-in

Cloudbeds does not provide a guest portal or online check-in product. D3x does not generate check-in or portal links on this connector. If a guest asks to check in online, the agent cannot open a Cloudbeds portal the way it can on Mews, or a Like Magic / P3 Hotels portal on Apaleo and Opera.

Outbound guest journeys

D3x still runs outbound guest journeys for Cloudbeds stays. The messages go out on WhatsApp, SMS, and email, not from a Cloudbeds-native guest portal.

Stay events

Journeys can fire at these points in the stay:

• Booking confirmation: when the reservation first lands in Cloudbeds
• Pre-arrival: before the guest arrives
• Check-in: when they check in, or around that moment
• Pre-departure: before checkout
• Checkout: when they leave, or around that moment

Audience filters

Not every reservation should get every message. D3x filters the audience so you segment who receives each send.

• Guest language
• Room type (include or exclude)
• Rate plan (include or exclude)
• Booking source
• Stay length / number of nights

This is the same outbound guest journey capability described on the WhatsApp docs and the Outbound page, for Cloudbeds reservations.

Go-live

Connecting Cloudbeds is a very simple go-live. The property authorises the D3x connection in Cloudbeds, and D3x is live. Most properties finish this in about two minutes.

1. In D3x, start the Cloudbeds connection.
2. The property authorises D3x in Cloudbeds.
3. D3x is connected to Cloudbeds for that property.

Keep Cloudbeds as the system of record. D3x sits above it as AI Agents for Hotel groups across channels. Book now goes into the Cloudbeds booking engine. Do not expect invoices or online check-in from this connector.