Kajabi Webhooks Without Zapier

Last updated November 21, 2026

If your host agency runs advisor onboarding in Kajabi, Kajabi can now tell JourneyFuse directly when something happens to an advisor. A purchase, a tag added or removed, or a form submission arrives at JourneyFuse and we act on it the same way your Zaps do today. You can turn those Zaps off once the webhooks are working.

What it can do

Each Kajabi event becomes one of the advisor lifecycle steps JourneyFuse already supports:

  • Sign up a new advisor when they buy your membership offer.
  • Activate their login when a tag such as "book ready" is added.
  • Rejoin a returning advisor.
  • Deactivate an advisor, and optionally block them from signing up again.
  • Grant or remove a badge (Academy, Coach, Partner and so on).
  • Record a referral from a form.

Which tag does what is a setting we keep for your agency, not something built into JourneyFuse. If you rename a tag in Kajabi, tell us the new name and we change the setting the same day; nothing has to be redeployed.

Setting it up

  1. Ask us for your webhook address. We create a private address for your agency, for example https://journeyfuse.com/api/agency/onboarding/kajabi/kji_…. Keep it private: Kajabi does not sign its webhooks, so the address itself is the key. If it ever leaks, we replace it.
  2. Tell us your rules, such as which tags activate, deactivate or badge an advisor, and which offers count as a signup.
  3. Create the webhooks in Kajabi using Kajabi's API (Settings → Public API for the key). Make one webhook for each event you use (purchase, tag_added, tag_removed, form_submission), with your address as the target. You can make a webhook for every tag or narrow it to one tag or one offer.
  4. Test with a test contact. Add a tag to a test contact in Kajabi and check the result with us. Kajabi's own "sample" test payload is accepted and never changes anything.
  5. Turn off the matching Zaps. It is safe to run both for a short overlap: each step only happens once per advisor, and the welcome email is never sent twice.

Good to know

  • Kajabi contact ID. Every webhook carries the advisor's Kajabi contact ID, which is how JourneyFuse recognises them. Advisors with no stored contact ID are matched by email.
  • Tags that don't match a rule are acknowledged and ignored, so you can use a wildcard webhook without worrying about every other tag in your Kajabi account.
  • Every webhook is logged, including ignored ones and any that failed, so we can tell you exactly what Kajabi sent and what happened.
  • Your existing Zapier setup keeps working. The direct webhooks are an addition, not a replacement you are forced into.

This is part of JourneyFuse’s host agency software: advisor workspaces, commission splits and agency-wide visibility.