Hello Hotel connects to Cloudbeds so your guests and reservations flow into your workspace automatically. When a guest calls or texts, your team sees their name, stay dates, room, and status without opening Cloudbeds — and your automations can run on reservation events.
For an overview of what the Cloudbeds integration does, see the Cloudbeds integration page.
Using Mews instead? See Connecting Mews PMS.
You'll need a Cloudbeds property and a Cloudbeds user who is allowed to authorize a connected app for it.
Everything happens from Hello Hotel. There are no API keys to create in Cloudbeds or paste anywhere.
Go to Settings → Integrations and open the Cloudbeds card. Choose to connect, and sign in to Cloudbeds when it asks you to — you're approving Hello Hotel's access to your property. Once you've approved it, your guests and reservations start syncing in.
You can also install Hello Hotel from the Cloudbeds Marketplace. The install lands on a Hello Hotel page where you sign in and pick which organization to connect.
When you connect, Hello Hotel imports reservations up to two years ahead — including bookings made before you connected that haven't been touched since — so pre-arrival automations and caller ID work for those guests too. No "new booking" messages fire for these older bookings.
Disconnecting in Hello Hotel also switches the app off in Cloudbeds, and switching it off in Cloudbeds disconnects Hello Hotel.
Once connected, you get the same guest context a Mews property gets:
Guest contacts — your guest contact book, matched by phone number, kept current as reservations change
Live reservation context — stay dates, room, and reservation status on the guest detail panel and in the conversation
Guest status labels — Future, Checking In, Checked In, In House, Checking Out, Checked Out, and Past — and repeat-guest flags
Booking source — shown as "Cloudbeds (source name)"
A link to the booking — each reservation on the guest detail panel links straight to that booking in Cloudbeds
Reservation notes and guest notes — synced both ways (details below)
Reservation changes normally land within seconds — Cloudbeds sends Hello Hotel a notification and it's applied as soon as it arrives. If that notification is missed, a background check every five minutes picks it up.
A booking created and never edited afterwards, and any note change, are things Cloudbeds doesn't send a notification for. The hourly sync catches them, so those can take up to an hour. (A note also refreshes the moment someone opens that reservation's notes in Hello Hotel.)
Room names and descriptions edited in Cloudbeds refresh within about six hours.
Need it now? Request a sync from the Cloudbeds card in Settings → Integrations. It queues and completes within a few minutes.
This matters for automations: a trigger that depends on a reservation change fires when the change reaches Hello Hotel, so a change Cloudbeds didn't notify us about can take up to an hour to fire its workflow.
Contact edits — edit a guest's contact details in Hello Hotel and they write back to Cloudbeds; edits made in Cloudbeds flow into Hello Hotel.
Guest merges — merge duplicate guests from the Contact conflicts screen, and the merge is applied in Cloudbeds too. See Contact Conflicts.
Reservation notes — view, add, edit, and delete a reservation's notes from the guest detail panel. Changes write straight back to Cloudbeds.
Guest notes — notes on the guest (not a single stay) sync in from Cloudbeds with their real dates, and a note you add in Hello Hotel is written to Cloudbeds. Guest notes are add-only from Hello Hotel: a Cloudbeds guest note can't be edited or deleted here, and Cloudbeds' note categories don't exist in Hello Hotel.
Good to know: Cloudbeds credits every note added through an integration to the person who connected it. So a note written in Hello Hotel appears in Cloudbeds prefixed with the writer's name — "[Ada Lovelace via Hello Hotel] Late arrival" — so your team can still see who wrote it. The prefix is stripped when the note is shown in Hello Hotel.
Reservations, rates, and folio data are never written to Cloudbeds, and payments always go through Cloudbeds. A contact you import from a CSV that doesn't already exist in Cloudbeds stays in Hello Hotel only.
Reservation variables work in messages, snippets, templates, and automations — first name, room name and description, stay dates, and booking source — plus two links:
Payment link — a Cloudbeds pay-by-link for the reservation's outstanding balance. It's created when the message is sent and stays valid for 30 days. It needs a positive balance, and it needs Cloudbeds Payments on your property: a property without Cloudbeds Payments gets a link that doesn't work, and Hello Hotel can't tell in advance.
Check-in link — a link to the Cloudbeds Guest Experience portal (formerly Whistle). It's off by default because Guest Experience is a paid Cloudbeds module Hello Hotel can't detect, and for a property without it the link is a dead login page. A manager turns it on with Guest Experience check-in links on the Cloudbeds card. This link is never shortened, even with URL shortening on.
There's no check-out link, digital key, pre-authorization link, add-card link, or room directions for Cloudbeds reservations — Cloudbeds has no equivalent to hand out — so those variables don't appear in the picker.
If your door codes are written into a Cloudbeds reservation custom field — by your team or by your lock system — Hello Hotel can use them. An owner or manager picks the field under Integrations → Cloudbeds → Door codes. Hello Hotel reads the 3–8 digit code from it ("ROOM 4: 0625" gives 0625) for stays in house or arriving within seven days, and fills the door code variable and the has door code condition. A booking with different codes for different rooms is skipped rather than guessed. With RemoteLock connected, Hello Hotel also checks the code and stay dates against RemoteLock. See Using Door Codes in Automations.
Reservation-driven triggers work the same way: New Reservation Created, Reservation Status Change, Check-in and Check-out Upcoming, and Guest Checked Out. Online Check-in Completed works too, once Guest Experience check-in links is switched on: Hello Hotel marks a stay as checked in online when the guest finishes pre-check-in in the Guest Experience portal and their card is on file (one card for a direct or Airbnb booking, two for an OTA booking whose channel card is already there). The Space Status Change trigger isn't offered for Cloudbeds, because Cloudbeds doesn't send housekeeping changes.
For conditions, use Room (clean or dirty, read live from the Cloudbeds housekeeping board) in place of Room (Space) Status. Card-on-file, pre-authorization, and identity-document conditions aren't available for Cloudbeds; the online-check-in conditions appear once Guest Experience check-in links is on. The editor hides what your PMS can't answer. See Using Conditions.
Availability and rate answers — AI Assist, the voice agent, and web chat room search — come straight from Cloudbeds' availability for the requested dates and party size, with taxes and fees included in the total. Only rates you've marked Active for Sources / Booking Engine in Cloudbeds are quoted, so the AI never names a rate your booking engine wouldn't sell. Availability answers carry a link to your Cloudbeds booking page, with the dates and party size filled in. The booking engine URL field in AI agent settings is optional for Cloudbeds: use it for the link you want the AI to share when a guest wants to book — usually the booking page on your own website.
Your property details and address, check-in and check-out times, room types (with how many each sleeps), occupancy, and amenities sync into the AI knowledge base every hour while the AI is on. Rates never go into the knowledge base — the agent always quotes them from a live availability check. Check-in and check-out times on reservations use your property's default times from Cloudbeds.
Cloudbeds decides who survives a merge. A merge is sent to Cloudbeds first, and Hello Hotel moves the conversation history once Cloudbeds confirms which profile survived. Some merges are refused with the reason shown — for example, profiles with reservations at another property — and offer Check again once you've fixed it in Cloudbeds. A merge that's waiting on Cloudbeds holds up only merges that touch the same contacts; others go ahead. See Contact Conflicts.
The link goes to the booking, not the guest. Cloudbeds has no guest-profile page to link to, so the guest detail panel links to each reservation instead.
Give it an hour before worrying. If a change you made in Cloudbeds hasn't shown up, it may be one of the hourly-sync cases above. Request a sync from the Cloudbeds card if you need it sooner.
Use the chat widget in the app, in this help center, or on hellohotel.co, or email us at [email protected].