Connect Track to ChatGPT.
Ask your Track 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 Larger US vacation-rental property managers running their portfolio on Track (TrackHS).
By Axelrod Labs · Updated June 2026
Ask Track operational questions without opening another dashboard.
Arrival board grouped by property and booking source.
Recent booking changes with arrival date, guest, and unit.
Balance-due list for front-desk follow-up.
Reservation totals by unit and channel.
ChatGPT uses a small private web connection to ask Track read-only questions. You own that connection; it only talks to Track when you ask ChatGPT something.
Connecting Track to ChatGPT
Yes, when you keep it read-only. Your Track Server API key and secret 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, Track admin access to obtain Track Server API key and secret, 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 Track bookings, guests, and calendar but cannot modify anything.
Plan on about 45-90 minutes if your Track Server API key and secret is ready. It can take longer when Track requires API approval, partner access, or workspace admin approval before ChatGPT can scan the connector.
Most common Track issue: the secret was not copied at creation time, so only the key is on hand and Basic auth fails with a 401. Track needs both the key and the secret. Copy both at creation time and store them securely, since you may not be able to view the secret again later.
Have these ready.
Budget about an hour for connector setup once credentials are ready. Add more time if you need API approval, partner access, or workspace admin approval.
Keep the first version boring and read-only.
Connect Track to ChatGPT in 4 steps.
Get your Track credentials
- In Track, open the configuration page with an admin account and go to the Company Setup tab, then API Keys.
- Click + Server Key, name it, save, and copy both the key and secret values.
- Confirm the key's scope can read reservations, units, and guests.
Set up the private connection
- Use a private Cloudflare Worker or managed setup path so PMS credentials stay outside ChatGPT.
- Paste your Track Server API key and secret into the prompted fields.
- Deploy the private connection and open the generated health page.
- Confirm it says Connected to Track before continuing.
Add it to ChatGPT
- Open ChatGPT settings.
- Go to Apps, open Advanced settings, and enable Developer mode.
- Create a custom app from the remote server URL shown on the health page.
- Complete the OAuth authorization screen.
Try operational prompts
- Open a new chat and select the app from Developer mode.
- Start with arrivals, departures, missing guest details, and occupancy questions.
Start with operational questions, not vague chatbot prompts.
Expected result: ChatGPT should answer with specific Track records: property names, reservation dates, guest fields it is allowed to read, and a clear note when data is missing.
Good for one property. Thin for a real portfolio.
ChatGPT can answer Track 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 Track'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.
Track issues first, generic OAuth issues second.
Track needs both the key and the secret. Copy both at creation time and store them securely, since you may not be able to view the secret again later.
Server API keys are scope-based. Confirm the scope grants read access to reservations and units before connecting, or requests will be rejected.
Most common Track issue: the secret was not copied at creation time, so only the key is on hand and Basic auth fails with a 401.
Developer mode is missing: confirm the ChatGPT account or workspace can create custom apps, and ask the workspace admin if the option is hidden.
OAuth popup blocked: allow popups for ChatGPT, then reconnect the app.
The app returns empty results: check that the PMS user or token can read all properties, reservations, and guests.
The app returns unauthorized: rotate the PMS credential, redeploy the private connection, then reconnect ChatGPT.