Scheduling & Booking · Integration
Cloudbeds
Add Cloudbeds to your product for your customers, and give your AI agents governed access to it.
Cloudbeds is property-scoped: one OAuth access token can cover several properties and almost every call to api.cloudbeds.com carries a propertyID, so an integration serving a group account has to enumerate properties first and then fan out per property rather than making one global call. The reservation is the anchor object and it holds one or more room stays, each with its own dates and rate, so a single booking can span rooms and cannot be flattened to one row without losing information. Availability and rate plans are managed separately from reservations, and changing a rate plan does not retroactively alter bookings already taken on it. API versions run in parallel under paths such as /api/v1.3 with older ones deprecated on a published timetable, and the scopes granted at authorisation decide which endpoints answer at all, so a missing reservation read scope looks like an empty property rather than an error. fastn runs the OAuth flow per property, refreshes tokens and keeps the granted scope set aligned with what each customer approved.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Cloudbeds property so bookings taken in your product are written straight into their PMS
Read arrivals and departures for the day to drive housekeeping or guest messaging in your application
Sync guest profiles and stay history so your CRM reflects who actually stayed rather than who booked
Pull availability and rates so a booking widget quotes what the property is really selling
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent to list tomorrow's arrivals with outstanding balances across a customer's properties, with each property read audited per tenant
Have an agent add a note or special request to an existing reservation on behalf of a front desk user
Let an agent compare occupancy against the same week last year for one property
Example prompt
Which reservations arrive tomorrow and still have a balance outstanding?
Set up Cloudbeds in 4 steps
- 01Enable the Cloudbeds connector from your fastn dashboard.
- 02Have each customer authorise their own Cloudbeds account, so calls run under their credentials rather than a shared key.
- 03Decide which bookings, events and availability your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Cloudbeds integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Cloudbeds integration without building it. Your customers connect their own Cloudbeds account inside your product and work their bookings, events and availability there, with no per-customer code on your side.
- Handle the part that actually costs time: availability is only true at the moment you read it, so a stale free/busy picture becomes a double booking somebody has to apologise for. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Cloudbeds update is not your on-call problem.
- One integration serves your product and your agents. The same governed Cloudbeds connection powers in-product features and gives AI agents scoped, audited access, so you let people book and reschedule without leaving your product without wiring it twice.
Used by these teams
Compare with
Calendly
Google Calendar
AppointletOften used alongside
Tools the same teams tend to run next to Cloudbeds, across other categories.
Slack
Microsoft Teams
Twilio
AircallCloudbeds integration FAQ
How do I add a Cloudbeds integration to my product?
Enable the Cloudbeds connector in your fastn dashboard, then let each customer authenticate their own Cloudbeds account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Cloudbeds client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Cloudbeds account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Cloudbeds account and only ever sees their own bookings, events and availability. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Cloudbeds integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent to list tomorrow's arrivals with outstanding balances across a customer's properties, with each property read audited per tenant
Who maintains the Cloudbeds integration?
fastn does. When Cloudbeds changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create, reschedule or cancel bookings in Cloudbeds automatically?
Yes, in each customer's own account. Your product reads live availability, places a booking, moves it or cancels it, and reacts when someone books or cancels on the other side.
Does it respect each team's own availability rules in Cloudbeds?
Yes. Working hours, buffers, lead times, resource capacity and routing rules are configured per customer and mapped rather than hard-coded, so an unusual setup works without code from you.
What can I build with the Cloudbeds integration?
A common starting point: let a customer connect their own Cloudbeds property so bookings taken in your product are written straight into their PMS. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Cloudbeds integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Cloudbeds does not change your per-connector cost. You can start free with 3 connected accounts.
Add Cloudbeds to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.