Connect Beds24 to ChatGPT.
Ask your Beds24 bookings, guests, and calendar questions in plain English. This guide shows the self-serve path first, then explains when Axelrod is the managed option.
For Operators using Beds24's flexible but technical PMS setup.
By Axelrod Labs · Updated June 2026
Ask Beds24 operational questions without opening another dashboard.
Date-sorted arrival list.
New booking list with property and channel.
Data-quality report for pre-arrival cleanup.
Property-level availability and booking count.
ChatGPT talks to your private Cloudflare Worker using MCP. The Worker stores the Beds24 token as a Cloudflare secret and exposes only read tools for properties, bookings, and room-calendar availability.
Connecting Beds24 to ChatGPT
Yes, when you keep it read-only. Your Beds24 API V2 token stays in a private connection you control, not inside ChatGPT, and this setup only reads data; it cannot create, change, or cancel reservations. Remove the ChatGPT app and delete the private connection to revoke access at any time.
Three things: a paid ChatGPT plan with Developer mode (or custom MCP connectors) enabled, Beds24 admin access to obtain Beds24 API V2 token, and a free Cloudflare account for the private connection.
No. This guide sets up a read-only connection, so ChatGPT can answer questions about your Beds24 bookings, guests, and calendar but cannot modify anything.
Plan on about 60-90 minutes the first time: most of the time is Cloudflare setup, creating the Beds24 token with the right read scopes, and scanning the Worker tools in ChatGPT.
ChatGPT cannot scan tools: confirm the Worker URL ends in /mcp, the Worker is deployed, and developer mode/custom apps are enabled for the ChatGPT account or workspace. Beds24 booking filters use the property's time zone. If arrivals look one day off, check the property time-zone settings first.
Have these ready.
This is self-serve, but it is not a one-click ChatGPT setting. You will deploy a small read-only Cloudflare Worker, then add it to ChatGPT as a custom MCP app.
Keep the first version boring and read-only.
Make sure ChatGPT can add the Worker.
Create the narrowest useful token.
The starter is read-only. Grant only the scopes needed for the questions you plan to ask.
In Beds24, API access must be allowed under Settings > Account > Account Access before API calls work.
Create the token under Settings > Marketplace > API. If using an invite code, exchange it for a token/refresh token before configuring the Worker.
Use read:properties so ChatGPT can map property and room names.
Use read:inventory so ChatGPT can answer availability and room-calendar questions.
Use read:bookings for booking dates, status, channel, and booking IDs.
Use read:bookings-personal only if you want ChatGPT to see guest names, phone numbers, email addresses, or message-related guest details.
Avoid write:*, delete:*, and all:* scopes for this read-only starter.
If your portfolio uses linked properties, enable Allow linked properties when creating the token. Beds24 does not include linked properties by default.
Connect Beds24 to ChatGPT in 5 steps.
Prepare the Beds24 token
- Use the checklist above to create a read-only Beds24 API V2 token or refresh token.
- Do not grant write:*, delete:*, or all:* scopes for this starter.
- Save the token in a password manager until Cloudflare asks for it.
Deploy the Cloudflare Worker
- Open the Worker starter README linked on this page.
- Download the worker-starter folder and run npm install.
- Set BEDS24_TOKEN or BEDS24_REFRESH_TOKEN as a Cloudflare Worker secret.
- Set CONNECTOR_BEARER_TOKEN as another Worker secret; use a random value and save it for ChatGPT.
- Run npm run check, then npm run deploy.
Confirm the health page
- Open the deployed Worker URL in a browser.
- Confirm it says the Beds24 credential and connector bearer token are configured.
- Copy the MCP server URL shown on the page. It should end in /mcp.
Add the Worker in ChatGPT
- Open ChatGPT on the web and enable developer mode or ask your workspace admin to do it.
- Create a custom app from Settings > Apps.
- Paste the Worker /mcp URL as the MCP server endpoint.
- If ChatGPT asks for auth, choose bearer/API key authentication and paste CONNECTOR_BEARER_TOKEN.
- Click Scan Tools, create the app, then select it in a new chat.
Run the first test
- Ask ChatGPT: Run the Beds24 access check.
- If it succeeds, ask for weekend arrivals or recent new bookings.
- If it fails, use the troubleshooting section below before widening token scopes.
Start with operational questions, not vague chatbot prompts.
Expected result: ChatGPT should answer with specific Beds24 records: property names, reservation dates, guest fields it is allowed to read, and a clear note when data is missing.
Download the Beds24 connector starter and PDF guide.
The written guide above is free. Enter your email to unlock the downloadable Cloudflare Worker starter files and the printable PDF.
This also tells Axelrod which PMS you use, so any follow-up is relevant.
Good for one property. Thin for a real portfolio.
ChatGPT can answer Beds24 questions. Axelrod turns the same booking data into morning briefs, guest-message drafts, cleaner handoffs, pricing nudges, and an approval queue across your stack.
Talk to AxelrodCheck Beds24's current API docs before connecting anything.
PMS settings and API permissions change. Use these links to confirm the exact credential names in the account you are working with.
Beds24 issues first, generic OAuth issues second.
Beds24 booking filters use the property's time zone. If arrivals look one day off, check the property time-zone settings first.
Beds24 API credit limits are account-level. Use narrow date ranges and avoid repeated broad prompts.
ChatGPT cannot scan tools: confirm the Worker URL ends in /mcp, the Worker is deployed, and developer mode/custom apps are enabled for the ChatGPT account or workspace.
Worker says unauthorized: ChatGPT is missing the bearer token or it does not match CONNECTOR_BEARER_TOKEN.
Beds24 says token is missing: set BEDS24_TOKEN or BEDS24_REFRESH_TOKEN as a Cloudflare Worker secret.
Beds24 returns a permission or scope error: create a new token or invite code with the missing read scope. Beds24 scopes are set when the token is created and cannot be changed later.
Guest names, phone numbers, or email fields are missing: recreate the token with read:bookings-personal.
Linked-property bookings are missing: recreate the token with Allow linked properties enabled.
Token expired: invite codes expire after 24 hours; generated tokens from refresh tokens expire after 24 hours; unused refresh tokens expire after 30 days; unused long-life tokens expire after 90 days.
Rate-limit error: narrow the prompt, avoid repeated broad date ranges, and wait for the five-minute credit window to reset.