# Cloudbeds integrations: reservations and guests

> Create a reservation, create a guest and assign a room in Cloudbeds, and start a workflow when Cloudbeds sends “Reservation created”.

**Canonical page:** https://tray.ai/connectors/cloudbeds-integrations/
**Categories:** Operations
**Connects through:** HTTP Connector

## Overview

Cloudbeds is a hotel management platform for independent properties and groups, combining a property management system, booking engine, channel manager, and guest records. Tray.ai connects to Cloudbeds through the HTTP Connector, so your workflows can call the Cloudbeds API alongside the rest of your stack.

## Use cases

### Reservations

Read, create, and update reservations in Cloudbeds from any Tray.ai workflow. The Cloudbeds API covers calls such as list reservations and get a reservation.

- List reservations
- Get a reservation
- Create a reservation

### Guests

Read, create, and update guests in Cloudbeds from any Tray.ai workflow. The Cloudbeds API covers calls such as list guests and get a guest.

- List guests
- Get a guest
- Create a guest

### Rooms

Read and update rooms in Cloudbeds from any Tray.ai workflow. The Cloudbeds API covers calls such as list rooms and assign a room.

- List rooms
- Assign a room
- Check in a room

### Rates

Read and update rates in Cloudbeds from any Tray.ai workflow. The Cloudbeds API covers calls such as list rate plans and get a rate.

- List rate plans
- Get a rate
- Update a rate

### Housekeeping

Read, create, and update housekeeping in Cloudbeds from any Tray.ai workflow. The Cloudbeds API covers calls such as get housekeeping status and update housekeeping status.

- Get housekeeping status
- Update housekeeping status
- Create a housekeeping assignment

### Payments

Read and create payments in Cloudbeds from any Tray.ai workflow. The Cloudbeds API covers calls such as list payment methods and record a payment.

- List payment methods
- Record a payment

## Challenges Tray.ai solves

### Keeping Cloudbeds credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Cloudbeds credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Cloudbeds API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Cloudbeds API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Cloudbeds?

Yes. Tray.ai connects to Cloudbeds through the HTTP Connector, which calls the Cloudbeds API directly. Any call the Cloudbeds API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Cloudbeds?

The Cloudbeds API uses an API key in a request header, a bearer token, and OAuth 2.0. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Cloudbeds connector?

Cloudbeds runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Cloudbeds connector from the Cloudbeds API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/