Last updated October 25, 2026
JourneyFuse has its own app on Zapier. With it you can send JourneyFuse activity to the rest of your tools (a new lead to Slack, a new booking to a Google Sheet, an accepted proposal to your accounting app) and bring records in from them (a lead from a website form, a client from a booking tool), all without code.
Find it at zapier.com/apps/journeyfuse/integrations, or search for JourneyFuse when you choose an app in the Zap editor. The app is public, so no invite link is needed. Zapier shows it with a Beta label for its first 90 days on the platform; it works the same as any other Zapier app.
You need two things:
jf_live_). It is shown only once.Use a key just for Zapier. If you ever want to cut Zapier off, revoke that one key and nothing else breaks.
You only connect once. Every Zap you build after that can reuse the same connection.
Triggers are instant: JourneyFuse tells Zapier the moment the event happens, rather than Zapier checking every few minutes.
| Trigger | Fires when |
|---|---|
| New Lead | A lead is created, by hand, from a form, or through the API |
| Lead Assigned | A lead is assigned to, accepted by, or moved between advisors |
| New Client | A client is created |
| New Trip | A trip is created |
| Trip Status Changed | A trip moves between statuses, for example Planning to Booked |
| New Booking | A booking is added to a trip |
| Payment Received | A payment is marked paid, recorded, or paid online by a client |
| Proposal Sent | A proposal is emailed to a client. Resends fire it too, with First send set to false |
| Proposal Accepted | A client accepts a proposal |
| Form Submitted | Someone submits one of your JourneyFuse forms |
When you test a trigger, Zapier pulls a recent real event from your workspace, so the fields you map are the ones your Zaps will actually receive. If nothing has happened yet, it shows a sample instead. Create a test lead or trip and test again to see your own data.
| Action | What it does |
|---|---|
| Create Lead | Adds a lead with name, email, phone, source, destination and notes. Only first and last name are required. |
| Create Client | Adds a client with name, email and phone. A new household is created for them unless you map an existing Household ID. |
| Create Trip | Adds a trip with a name, client, destination, dates and status (Planning by default). Pick the client from the dropdown, or map a client ID from an earlier step. |
| Find Client | Looks up a client by email, ignoring capitals. Use it before Create Trip to attach the trip to the right person. |
A common pattern for booking or intake forms: Find Client by email, then Create Trip for that client. If the person might be new, add a Zapier filter or path that runs Create Client when Find Client comes back empty.
A Zap sees exactly what its API key can reach:
The full rules are in API & Make.com / Zapier Integration.
Zapier says the key is invalid. Check that you copied the whole key, starting with jf_live_, and that it hasn't been revoked on the Settings → API Keys page. If in doubt, create a new key and reconnect.
A Create step fails with a permission error. The key is read-only. Create a key with Read-only unticked and reconnect the account in Zapier.
A trigger never fires for some records. The key probably belongs to an advisor, so it only sees that advisor's records. Use an owner or admin key for agency-wide Zaps.
An advisor's Zaps stopped working. An owner or admin may have turned off Advisor integrations under Settings → API Keys. While it is off, advisors' keys are refused and their Zaps receive nothing.
A Zap fires many times at once. A large import or bulk edit creates many events together. Zapier may throttle or pause a Zap during a burst. Turn the Zap off before a big import and back on afterwards.
This is part of JourneyFuse’s travel agency software: team roles, permissions and agency-wide settings.
Automatically send real-time event data to external tools like Zapier, Make.com, or your own API whenever something happens in JourneyFuse.
Read and write your leads, clients, trips, bookings, and quotes from your own scripts or no-code tools like Make.com and Zapier using the JourneyFuse REST API.
Ask Claude or ChatGPT about your agency's JourneyFuse data: advisor status, lead assignments, commissions, group requests and suppliers. Read only, signed in as yourself, and never any client details.