Offer configuration stays visible
Use Offers to decide what Kajabi receives: product, price, buyer, checkout mode, invoice, and automation context.

Integration
Course and membership delivery for creators who want Plandalf to own the buying path.
Product surfaces
Integrations work best when the checkout surface, payment state, invoice record, and post-purchase automation all point at the same commercial object. These product screens show the Plandalf controls that should be configured before Kajabi receives checkout, payment, tax, or workflow context.
Use Offers to decide what Kajabi receives: product, price, buyer, checkout mode, invoice, and automation context.
Before Kajabi enters the stack, operators still need checkout templates, products, prices, coupons, order bumps, upsells, and branded offer content they can inspect.
Kajabi should fit into the work after checkout: fulfilment, records, CRM updates, support context, webhooks, and sequences.
Builder paths
Use these stack guides when a builder needs the whole path: sales surface, Plandalf offer, payment handoff, automation, fulfilment, records, and downstream integrations.
Find full stack guides that pair Kajabi with checkout, payment, automation, fulfilment, records, and downstream integrations.
Use Offers to package products, prices, checkout pages, invoices, coupons, payment options, and follow-up context.
Use hosted checkout when Kajabi should hand the buyer to a branded Plandalf checkout page.
Use SDK checkout when Kajabi belongs inside an app, custom site, or API-first stack.
Route checkout events, purchase events, payment state, invoices, and customer context into another tool.
Turn a completed checkout into access, receipts, CRM updates, support context, and records.
Compare how Kajabi fits beside Plandalf Offers, checkout, payment state, invoices, automation, and integrations.
Compare how Kajabi fits beside Plandalf Offers, checkout, payment state, invoices, automation, and integrations.
Kajabi can stay the place where course content, memberships, and customer access live. Plandalf sits in front of it as the offer and checkout layer: the product page sends buyers into a Plandalf Offer, Stripe or PayPal handles payment, and the purchase event can grant access or trigger the Kajabi-side fulfillment path.
This is the cleanest fit when the course experience already lives in Kajabi, but the launch needs a more flexible checkout, order bump, payment option, deadline, receipt, or post-purchase workflow.
Automation graph
How Kajabi participates in Plandalf sequences: what events it exposes upward, and what actions Plandalf can perform on it.
Events Plandalf can subscribe to through webhooks, API work, checkout state, payment context, and connected integrations.
kajabi.subscriber_addedThings Plandalf sequences can do after checkout, payment, invoice, customer, or deadline events.
trigger: stripe.payment_succeeded
actions:
- kajabi.add_subscriber:
list: paying-customers
tag: tier-${plan}
- plandalf.grant_entitlement: ${product_slug}Pair it with
Platforms whose roles complement Kajabi inside a Plandalf sequence.
Kajabi + ActiveCampaign
Compose Kajabi and ActiveCampaign programmatically via the Plandalf SDK.
Kajabi + beehiiv
Compose Kajabi and beehiiv programmatically via the Plandalf SDK.
Kajabi + Kit (ConvertKit)
Compose Kajabi and Kit (ConvertKit) programmatically via the Plandalf SDK.
Kajabi + Customer.io
Compose Kajabi and Customer.io programmatically via the Plandalf SDK.
Kajabi + Drip
Compose Kajabi and Drip programmatically via the Plandalf SDK.
Kajabi + Flodesk
Compose Kajabi and Flodesk programmatically via the Plandalf SDK.
Integration methods
Each method below is the minimum viable setup. Pick the one closest to how you already use Kajabi with checkout, payments, invoices, webhooks, API work, SDK checkout, and integrations.
Kajabi doesn't expose a recognized capability above, so wire it up through the Plandalf REST API — POST events in, GET state out.
curl -X POST https://api.plandalf.com/v1/events \
-H "Authorization: Bearer $PLANDALF_API_KEY" \
-H "Content-Type: application/json" \
-d '{"source": "kajabi", "type": "custom", "data": {}}'FAQ
Plandalf itself is free to connect to Kajabi. You only need a Kajabi account that allows API access, which is almost every paid plan.
Under 10 minutes — paste a webhook URL into Kajabi, point it at the Plandalf endpoint, and trigger a test event to confirm.
Yes. Disconnecting only revokes the credentials — historical events Plandalf fired stay in your sequence logs, and Kajabi's own records are untouched. You can reconnect any time and resume from the last seen event.
Plandalf stores the minimum IDs needed to address a record in Kajabi plus a log of events Plandalf fired. Source-of-truth data stays in Kajabi.
Drop into the Plandalf REST API and call Kajabi directly from your sequence's HTTP action. Anything Kajabi's public surface exposes is reachable.
There's no Plandalf-side limit. Kajabi's own plan limits apply.
Kajabi's homepage at https://kajabi.com links to their developer docs. For Plandalf-side questions about the Kajabi integration, see the Plandalf docs.