Webhooks

Webhooks let JourneyFuse push data to other tools the moment something happens — a new lead comes in, a payment is received, a trip status changes. Instead of manually copying data between systems, webhooks do it automatically in real time.

Think of it as JourneyFuse tapping another tool on the shoulder and saying "hey, this just happened" — along with all the details.

What Are Webhooks?

When an event occurs in JourneyFuse, a webhook sends an HTTP POST request with a JSON payload to a URL you specify. That URL can be:

• A Zapier or Make.com webhook trigger (no coding required)
• A custom API endpoint you've built
• Any service that accepts incoming webhooks

Each delivery includes:

• The event type (e.g., lead.created)
• A timestamp of when it happened
• The event data (lead details, trip info, payment amount, etc.)
• An HMAC-SHA256 signature so you can verify it came from JourneyFuse

Supported Events

Event	Fires When
Lead Created	A new lead is added — manually or from a website form
Client Created	A new client is added to your CRM
Trip Created	A new trip is created for a client
Trip Status Changed	A trip moves between stages (lead → booked → completed → closed)
Booking Created	A reservation is added to a trip (flight, hotel, cruise, etc.)
Payment Received	A payment is marked as paid
Commission Updated	A commission entry is modified (amount, status, dates)
Task Completed	A task is marked as completed

Setting Up a Webhook

1. Go to Settings → Webhooks
2. Click Add Webhook
3. Enter the Endpoint URL — this is where JourneyFuse will send data
4. Optionally add a Description so you remember what it's for
5. Select which events you want to subscribe to (or click "Select All")
6. Click Add Webhook

Your webhook is now active. Use the Send test payload button to verify your endpoint is receiving data correctly.

What Your Webhook Receives

Scope follows whoever created the webhook, which matters most at a host agency where many advisors share one workspace.

Who created it	What it receives
An advisor on a team	Events for that advisor's own clients, leads, and trips
An agency owner or admin	Every event in the workspace
A solo agency	Everything, since it is all yours anyway

So an advisor's Slack channel or Zap never sees a colleague's leads, and the agency's own reporting webhook still sees the full picture. Owners and admins see every webhook in the workspace on this page; advisors see only their own.

Example: New Leads to Slack via Zapier

Want a Slack message every time a new lead comes in from your website?

1. In Zapier, create a new Zap with Webhooks by Zapier as the trigger → choose "Catch Hook"
2. Copy the webhook URL Zapier gives you
3. In JourneyFuse, go to Settings → Webhooks → Add Webhook
4. Paste the Zapier URL and subscribe to Lead Created
5. Click "Send test payload" to send sample data to Zapier
6. Back in Zapier, add a Slack action → choose your channel → map the fields:
   • Message: New lead: {{data__first_name}} {{data__last_name}} ({{data__email}}) — Source: {{data__source}}
7. Turn on the Zap

Now every website form submission instantly notifies your team in Slack.

Example: Payments to Google Sheets via Make.com

Track every payment in a shared spreadsheet automatically:

1. In Make.com, create a new scenario with Webhooks → "Custom webhook" as the trigger
2. Copy the webhook URL
3. In JourneyFuse, add a webhook subscribed to Payment Received
4. Send a test payload so Make.com can learn the data structure
5. Add a Google Sheets module → "Add a Row"
6. Map the fields: amount, payment type, paid date, trip ID
7. Activate the scenario

Every time a payment is marked as paid, a new row appears in your spreadsheet — no manual entry.

Example: Booking Confirmations to QuickBooks

Automatically create draft invoices when bookings are added:

1. Set up a Zapier webhook trigger subscribed to Booking Created
2. Add a QuickBooks Online action → "Create Invoice"
3. Map: supplier name, total price, confirmation number, dates
4. Any new booking with a price automatically generates a draft invoice in QuickBooks

Example: Task Completion to ClickUp

Keep your project management in sync — when a task is completed in JourneyFuse, automatically update ClickUp:

1. In ClickUp, go to Settings → Integrations → Webhooks or use a Make.com/Zapier connection
2. In JourneyFuse, add a webhook subscribed to Task Completed
3. In your automation tool, add a ClickUp action → "Update Task Status" or "Create Comment"
4. Map the task title and completion status

Your ClickUp board stays up-to-date without anyone switching between apps.

Example: Trip Status to HubSpot CRM

Automatically move deals through your CRM pipeline when trip stages change:

1. Set up a Zapier webhook trigger subscribed to Trip Status Changed
2. Add a HubSpot action → "Update Deal Stage"
3. Map the trip status to your deal stages: lead → qualified → booked → won
4. Every status change in JourneyFuse automatically updates the CRM

Your sales pipeline stays accurate with zero manual entry.

Security: Verifying Webhook Signatures

Every webhook delivery includes an X-JourneyFuse-Signature header containing an HMAC-SHA256 hash of the request body, signed with your webhook's secret key. If you're building a custom integration, you should verify this signature to ensure the request actually came from JourneyFuse.

Your webhook secret is generated automatically when you create a webhook and is visible in the webhook settings.

Delivery History

Each webhook shows its recent delivery history — you can see:

• Which events were sent
• The HTTP status code from your endpoint
• Whether delivery succeeded or failed
• When each delivery was attempted

If a delivery fails (your endpoint returns a non-2xx status or times out), JourneyFuse records the failure. Each delivery is retried up to 3 times immediately for temporary problems — a timeout, a network error, or a 5xx from your endpoint. You can also use the test button to retry manually.

When an endpoint stops responding

A webhook is never switched off because it failed. If your endpoint rejects 15 deliveries in a row — usually because the Zap was turned off, or the URL was deleted or changed — the webhook stays on but goes into a cooldown, and you'll see a red Retrying badge with the time of the next attempt.

While it's in cooldown we keep trying on a widening schedule (starting a minute out, up to once an hour). The moment one delivery succeeds, everything resets and normal delivery resumes on its own — there's nothing to switch back on. If you've just fixed your endpoint and don't want to wait, hit Send test: a successful test clears the cooldown immediately.

Events that occur while a webhook is in cooldown are not queued or replayed. If your endpoint was down for a while, check the delivery history to see what you missed.

A burst of events is the usual culprit. A large import or bulk update can fire hundreds of events at once, and Zapier and Make.com will throttle or switch off a hook that gets flooded — that's the most common reason a working webhook suddenly starts failing. If one goes into cooldown right after a big change on your side, check whether the Zap itself is still turned on.

Tips

• Start with one event — get it working, then add more
• Use the test button before relying on a webhook in production
• Zapier and Make.com are the easiest way to connect webhooks without any coding
• Disable rather than delete — use the toggle switch to pause a webhook temporarily without losing your configuration. The toggle is now the only thing that turns a webhook off; we never do it for you
• If your endpoint is down, deliveries fail and the webhook backs off rather than switching off — check your delivery history if you suspect missed events