Linking Cloudbeds as a source
Let AI connect your sources for you
Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.
This source is currently in alpha. The interface and available tables may change.
The Cloudbeds connector syncs hotels, reservations, guests, and more into the PostHog data warehouse, so you can analyze them alongside your product data.
Prerequisites
Credentials that can read the data you want to sync. PostHog only reads data, so read access is enough.
Adding a data source
- In PostHog, go to the Sources tab of the data pipeline section.
- Click + New source and click Link next to this source.
- Enter your credentials (see Configuration below) and click Next.
- Select the tables you want to sync, choose a sync method and frequency, then click Import.
Once the syncs are complete, you can start querying this data in PostHog.
Enter your Cloudbeds API key to pull your properties, reservations, guests, rooms, room types, and transactions.
You can create an API key under Settings → API credentials in Cloudbeds. Note that Cloudbeds API keys expire after 30 days of inactivity, so a key that has not been used recently may need to be regenerated.
If your account manages multiple properties, enter the ID of the property you want to sync - group-level credentials require it to scope reads to a single property.
You'll be asked for:
- API key
Sync modes
Each table can be synced in one of several modes, depending on what the source supports:
- Webhook (when available) – the source pushes changes to PostHog in real time. Fastest freshness, lowest ongoing cost, and the only mode that reliably captures updates and deletes.
- Incremental – only new or updated rows are synced on each run, using a cursor field (such as an
updated_attimestamp). Cheaper than a full refresh, but deletes aren't captured. - Append only – new rows are appended using a cursor field; existing rows are never updated. Ideal for immutable, append-only tables like event logs.
- Full refresh – the whole table is reloaded on every sync. Use it when a table has no reliable cursor or when you need deletions reflected.
See sync methods for a full explanation of how each mode works and how to choose between them.
All Cloudbeds tables are full refresh. Each sync replaces the contents of the table.
Configuration
| Option | Type | Required |
|---|---|---|
API key | password | Yes |
Property ID (required for multi-property accounts) | text | No |
Supported tables
| Table | Description | Sync method | Incremental field | Primary key |
|---|---|---|---|---|
hotels | A property (hotel, hostel, or vacation rental) managed by the Cloudbeds account. | Full refresh | — | — |
reservations | A booking at a property, covering one or more rooms and guests. | Full refresh | — | — |
guests | A guest profile stored at the property, linked to one or more reservations. | Full refresh | — | — |
rooms | A physical room (or unit) at a property, listed per property by the rooms endpoint. | Full refresh | — | — |
room_types | A room category at a property (e.g. double, dorm bed) with its occupancy and inventory settings. | Full refresh | — | — |
transactions | A financial transaction (charge, payment, tax, or adjustment) posted at the property. | Full refresh | — | — |
reservations_with_rate_details | A booking at a property with the rates, source, and per-room details behind it, including the daily rate of each booked room. | Full refresh | — | — |
rate_plans | A rate a property sells, resolving the rate IDs carried on reservations to their rate plan and room type. Rate and availability columns cover a rolling one-month window from the sync date. | Full refresh | — | — |
users | A staff user with access to a property, resolving the user IDs stamped on transactions and reservation changes. A user working at several properties in a group account has one row per property. | Full refresh | — | — |
Troubleshooting
- If the connection fails with an authorization error, the API key is wrong, expired, or has been revoked. Create a new one, then reconnect the source.
- If a table syncs no rows, the credential may not have access to that data. Check its permissions, then reconnect the source.
If your sync is failing or data looks wrong, see the Data warehouse troubleshooting guide. If that doesn't help, contact support – we're happy to help.