Thrivecart + Kajabi: The Setup Guide for Course Creators

Step 1: Connect Thrivecart to Kajabi

• ●In Thrivecart, open Settings and then the integrations area (API & Webhooks at the time of writing)
• ●Find Kajabi in the list of integrations and click Connect
• ●Authenticate with your Kajabi credentials and approve
• ●Thrivecart should pull in your offers and tags. If a new offer does not appear, refresh the connection before you assume something is broken

Step 2: Map products to Kajabi offers

On each Thrivecart product, open Behaviour (or Fulfilment, depending on your version). Add a new behaviour:

• ●Trigger: When customer purchases this product
• ●Action: Grant access to a Kajabi offer (select the offer)
• ●Optional: Add a Kajabi tag (useful for email sequences)
• ●Save, then test it using the method in the testing section below before you send traffic to the checkout

Step 3: Handle refunds properly (this is where access leaks)

If the refund behaviour is not set, refunded customers keep access to your course. It is the setting I most often find missing when I audit a Thrivecart and Kajabi account.

On the same Behaviour screen, add a second behaviour:

• ●Trigger: When customer is refunded
• ●Action: Revoke Kajabi offer access
• ●Optional: Remove the purchase tag and add a 'refunded' tag for analytics
• ●Check Thrivecart's documentation for what happens on a partial refund and on a subscription cancellation. They are separate events, and the revoke behaviour may not cover all of them

Bump offers and upsells

Each bump and upsell product gets its own behaviour. So if your main product unlocks Offer A, your bump unlocks Offer B, and your upsell unlocks Offer C, you set up three separate behaviour blocks, each with its own refund behaviour. Tedious but not complicated.

Check the supported route before building

Confirm the current trigger, action and account requirements in the platform's official documentation. Map the required fields and define what should happen for a successful event, a missing value, a duplicate event and a failed handoff. Test the agreed paths using an appropriate test method, then document the result and who will review exceptions.

For Thrivecart and Kajabi, use the test method Thrivecart supports rather than a live purchase with a real card. Thrivecart has a test mode for running a checkout without charging; check its documentation for how to switch it on, what it does and does not send to integrations, and how to run a test refund. A live purchase on a real card is a last resort, and if you use one, refund it through Thrivecart so the refund path gets tested too. The cases to run:

• ●Successful purchase: the test buyer appears in Kajabi with the right offer and tag, and receives the Kajabi welcome email
• ●Missing value: a buyer whose email already exists in Kajabi under different capitalization, or a purchase with a name field left blank. Confirm access is still granted to the right person
• ●Duplicate event: the same buyer purchases the same product twice, or Thrivecart resends the notification. Confirm Kajabi does not create a second member or a second welcome sequence
• ●Failed handoff: disconnect the integration or use an offer that no longer exists, then buy. Find where the failure shows up in Thrivecart and who would see it
• ●Refund: refund the test purchase and confirm access is revoked and the tags change as expected
• ●Write down what you tested and who checks Thrivecart's integration logs when a buyer says they cannot get in