Connect an AI Assistant to JourneyFuse

You can point an AI assistant at your JourneyFuse account and ask it things like "which trips depart in the next 30 days and still owe a final payment?" or "draft a check-in email for everyone travelling next week." It reads your real records through the JourneyFuse API, so its answers come from your actual book of business instead of whatever you remembered to paste into the chat.

This works with Grok, ChatGPT, Claude, Gemini, or anything else that can call a web address with a key. None of them need a special JourneyFuse plugin.

Read the safety section before you set this up. An API key can read your clients' passport numbers, dates of birth, and Known Traveler numbers. Handing that to an outside AI service is a real decision, not a formality, and the section below is the short version of what you are agreeing to.

What It Can Do

It can read	It can create or update	It cannot do
Clients, trips, leads	Leads	Add a hotel, flight, or cruise to a trip
Bookings (hotels, flights, cruises)	Clients	Create or edit a quote
Quotes and where each one stands	Trips	Send an email or invoice on your behalf
	Ask a client for their own details	Delete a client, trip, booking, quote, or lead

No endpoint deletes a client, trip, booking, quote, or lead, and nothing here emails your clients on its own. The worst an assistant can do by mistake is create a duplicate lead or overwrite a field on a record it already created.

Setting It Up

1. Create a key for the assistant

Go to Settings → API and click New API key. Name it after the assistant, not after yourself, so you can tell later which one to revoke. The key appears once and starts with jf_live_.

Give the assistant a separate key from any key you use for Make.com or Zapier. When you want to cut the AI off, you revoke one key and nothing else breaks.

2. Tell the assistant where to look

Most tools want three things:

Base URL — https://journeyfuse.com (or your own domain if you have one)
Auth header — Authorization: Bearer jf_live_your_key_here
What is available — point it at https://journeyfuse.com/kb/team-settings/api

That documentation page lists every endpoint, field, and filter, so a capable assistant can usually work out the rest on its own once it can reach it.

3. Check it worked

Ask it to call GET /api/v1/me. That returns your workspace and confirms the key is live without touching any client data. If it comes back 401, the key is wrong or was revoked. If it comes back 404, the address is wrong.

The Two Mistakes AI Assistants Make Here

These are not JourneyFuse problems, but they will look like JourneyFuse problems when they happen.

It reads the first page and reports it as the whole picture

Lists return up to 100 records at a time. When there are more, the response includes a next_cursor, and the assistant is supposed to ask again with that cursor until it stops coming back.

An assistant that skips this will not tell you it only saw part of your data. It will confidently say you have 100 clients when you have 340, or that nobody has a payment due when the ones that do were on page two. If a number it gives you looks low, this is almost always why. Tell it explicitly: "keep following next_cursor until there are no more pages, then answer."

It invents a field name when creating a record

If it sends customer_name where the field is first_name, JourneyFuse does not silently drop it. Every create and update response carries an ignored_fields list naming anything it did not recognise, and a body with no usable fields at all comes back as an error rather than a cheerful success.

So if an assistant is creating clients or leads that end up half empty, have it read ignored_fields back to you. It is the fastest way to find a wrong field name, and it only appears on writes, not on reads.

Safety

An API key is a password. Anyone holding it reads your workspace as you.

Your clients' private details are inside. The client record carries dates of birth, passport numbers and expiry dates, Known Traveler and Redress numbers, and home addresses. An assistant with a key can read all of it, which means the company running that assistant can process it too. Check what their service does with the data it sees, and whether your clients would expect it to go there. If you are not comfortable with that, this is the point to stop.

Never paste a key into a normal chat message. Put it in the tool's connection or credential settings, where it is stored as a secret. A key typed into a conversation lives in that conversation's history, and often in the provider's logs.

Give it the smallest key that does the job. If you are on a team, a key you create as an advisor reaches only your own clients, leads, trips, bookings, and quotes, never a colleague's. An owner or admin key reaches the entire agency. For a personal assistant, the advisor key is almost always the right one.

Revoke it when you are done experimenting. Settings → API, and the key stops working immediately. Create a fresh one later. Revoking costs nothing and there is no limit on how many you make.

Watch the last-used date. The Settings → API page shows when each key was last used. A key you thought you had finished with that is still being used every day is worth a second look.

API & Make.com / Zapier Integration — every endpoint, field, and filter
Webhooks — have JourneyFuse push events out as they happen, instead of the assistant polling
Automations — for scheduled client emails, which JourneyFuse does better on its own than through a bot