> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/other/cloudbeds.md).

# Cloudbeds

Cloudbeds is an all-in-one hospitality management platform used by hotels, hostels, and vacation rentals to manage reservations, guests, rooms, and payments. Connecting Cloudbeds to Coupler.io lets you pull your property data into any destination for reporting, analysis, or AI-powered workflows.

## Why connect Cloudbeds to Coupler.io?

* **Centralize your property data** — combine reservations, transactions, guests, and room inventory in one place
* **Automate reporting** — send live data to Google Sheets, Looker Studio, BigQuery, or Excel without manual exports
* **Unlock AI insights** — pipe your hospitality data into ChatGPT, Claude, Gemini, or Perplexity to analyze trends and answer questions
* **Combine multiple entities** — use Join or Append transformations to merge reservations with guest profiles or transaction records

## Prerequisites

* An active Cloudbeds account
* A Cloudbeds API key (generated from your Cloudbeds developer settings)
* Access to the property or properties you want to export

## Quick start

{% hint style="success" %}
Start with the **Reservations** entity — it's the most commonly used and connects naturally with Guests and Transactions for a full booking picture.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Log in to your Coupler.io account and click **Add data flow**. Search for and select **Cloudbeds** as your source.
{% endstep %}

{% step %}
**Enter your Cloudbeds API key.** In the source settings, paste your Cloudbeds API key into the API key field. You can find this in your Cloudbeds account under **Settings > API > Generate API key**.
{% endstep %}

{% step %}
**Select an entity.** Choose which data you want to import — Guests, Hotels, Rooms, Reservations, Transactions, or Packages.
{% endstep %}

{% step %}
**Choose a destination.** Select where you want your data to land — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like ChatGPT, Claude, or Gemini.
{% endstep %}

{% step %}
**Run your data flow.** Click **Run** to execute the data flow manually. Once it completes successfully, your Cloudbeds data will appear in your chosen destination.
{% endstep %}
{% endstepper %}

## Available entities

| Entity       | Description                                 |
| ------------ | ------------------------------------------- |
| Guests       | Guest profiles and contact information      |
| Hotels       | Property details and configuration settings |
| Rooms        | Room inventory, types, and availability     |
| Reservations | Booking records and reservation details     |
| Transactions | Financial transactions and payment records  |
| Packages     | Service packages and add-on offerings       |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.coupler.io/sources/category/other/cloudbeds.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.