Kajabi

Integration

Kajabi

Course and membership delivery for creators who want Plandalf to own the buying path.

What it does

  • Course and membership delivery
  • Product access after purchasePurchase automations
  • Creator site and email tools

Product surfaces

Where Kajabi fits in the buying workflow

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.

The Numi offer editor showing layout, product, theme, automation, invoice, and settings controls.
The Numi checkout elements palette showing content, interactive, and selling blocks.
The Numi offer editor automation tab showing sequence controls beside the checkout canvas.

Purchase events can start follow-up

Kajabi should fit into the work after checkout: fulfilment, records, CRM updates, support context, webhooks, and sequences.

Builder paths

Stack guides that use Kajabi

Use these stack guides when a builder needs the whole path: sales surface, Plandalf offer, payment handoff, automation, fulfilment, records, and downstream integrations.

Overview

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

Connecting Kajabi

How Kajabi participates in Plandalf sequences: what events it exposes upward, and what actions Plandalf can perform on it.

Triggers from Kajabi

Events Plandalf can subscribe to through webhooks, API work, checkout state, payment context, and connected integrations.

kajabi.subscriber_added
Fires when a new subscriber is added to Kajabi.

Actions on Kajabi

Things Plandalf sequences can do after checkout, payment, invoice, customer, or deadline events.

kajabi.add_subscriber
Add a contact to a list or audience in Kajabi.
kajabi.tag
Apply a tag or segment to an existing Kajabi contact.
kajabi.send_email
Send a one-off transactional or broadcast email through Kajabi.
kajabi.grant_access
Enrol a customer into a course or membership level in Kajabi.
Example sequence
trigger: stripe.payment_succeeded
actions:
  - kajabi.add_subscriber:
      list: paying-customers
      tag: tier-${plan}
  - plandalf.grant_entitlement: ${product_slug}

Integration methods

How Kajabi connects to Plandalf

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.

  1. Method 1

    Integrate via the Plandalf REST API

    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": {}}'
Official Kajabi docs and sign-up: kajabi.com

FAQ

Common questions about the Kajabi integration

Do I need a paid plan to use Kajabi with Plandalf?

Plandalf itself is free to connect to Kajabi. You only need a Kajabi account that allows API access, which is almost every paid plan.

How long does setup take?

Under 10 minutes — paste a webhook URL into Kajabi, point it at the Plandalf endpoint, and trigger a test event to confirm.

Can I disconnect Kajabi later without losing data?

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.

Does Plandalf store Kajabi data?

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.

What if my lms need isn't covered by the actions or triggers listed here?

Drop into the Plandalf REST API and call Kajabi directly from your sequence's HTTP action. Anything Kajabi's public surface exposes is reachable.

Is there a usage limit?

There's no Plandalf-side limit. Kajabi's own plan limits apply.

Where do I find Kajabi's own documentation?

Kajabi's homepage at https://kajabi.com links to their developer docs. For Plandalf-side questions about the Kajabi integration, see the Plandalf docs.

Feature detail