If you searched for this, you have probably already hit the confusing part: there is no single “Kajabi to ConvertKit” integration.
There are 3 different ways to connect the two, they do very different things, and most of them depend on which Kajabi plan you are on.
So before anything else, the one piece of housekeeping that trips people up: ConvertKit is now Kit.
Here is a simple tool to help you determine which route to go:
The 3 methods at a glance
If you want the short version, this table is it. The rest of the article is just the detail behind each row.
| Method | What it actually moves | Plan needed | Best for |
|---|---|---|---|
| Native form connector | Form opt-ins only (email and name to a Kit form) | Any plan | Simple lead capture |
| Webhooks to Kit | Purchase and event data, no Public API needed | Growth / Pro | Event triggers on a budget |
| Zapier | Same events as webhooks, no-code, 6,000-app bridge | Growth / Pro | Non-technical setups |
| Kit's native Kajabi app | Full sync: students, tags, purchases, automation triggers, grant-back | Public API (free on Pro, $25/mo add-on on Basic or Growth) | Full lifecycle automation |
A quick note on plans: some long-time Kajabi users are on legacy plans that retained features (including API access) from before the September 2025 restructure, so your account may behave differently than the current tier names suggest. Where that matters below, we flag it.
Method 1: The native form connector (any plan)
This is Kajabi’s built-in connection, and it is the only method that works no matter what you are paying.
It does exactly one thing: when someone submits a Kajabi opt-in form or goes through a checkout, their email and name get passed to a Kit form.
How to set it up:
In Kit, create the form you want submissions to land in, and grab its Form ID from the form’s page URL.
In Kajabi, open Settings, then Third Party Integrations, and toggle on ConvertKit.
Paste in your Kit API Key and save.
Edit the Kajabi form you want connected, check “Send the contact to a third party email provider,” select ConvertKit, and paste the Form ID.
Save, then test by submitting the form with a real email address.
Watch the double opt-in trap
If double opt-in is enabled on both the Kajabi form and the Kit form, your subscriber gets two separate confirmation emails and is far more likely to bail before confirming. Turn double opt-in off on the Kajabi side and let Kit handle confirmation alone.
Limitation
The native connector cannot send tags, cannot tell Kit what someone purchased, and cannot trigger a Kit automation off a purchase or course-access event. It forwards form opt-ins, full stop.
For a lead magnet feeding a welcome sequence, that is all you need.
Method 2: Webhooks to Kit (Growth and Pro)
This is the cheapest way to move actual purchase and event data without buying the Public API add-on.
Kajabi can fire an outbound webhook whenever someone submits an opt-in form, purchases an offer, or completes an assessment.
You point that webhook at Kit, and now your email platform knows when money changes hands, not just when someone fills in a form.
Plan requirement
Per Kajabi’s own documentation, webhooks are available only on the Growth and Pro plans. If you are on Basic, this method is off the table unless you are on a legacy plan that included webhooks. There is no webhook-only add-on; you either need the plan tier or you fall back to Method 1.
Webhooks are the right call when you want purchase-triggered email behavior, you are already on Growth or Pro, and you do not want to pay the extra $25 a month for the full Public API integration.
You give up the deep two-way sync, but for “someone bought X, start sequence Y” you do not need that depth.
Method 3: Zapier (Growth and Pro, in practice)
Zapier sits one layer above raw webhooks.
You can connect Kajabi to Zapier with your API Key and Secret, then build no-code automations that listen for Kajabi events and push them into Kit, or into any of the roughly 6,000 other apps Zapier supports.
Zapier’s setup docs say any paid Kajabi plan can connect, which is technically true for the connection.
But the Kajabi triggers that make a Zap useful, New Purchase, Cart Purchase, New Form Submission, Assessment Completed, are built on Kajabi’s outbound webhooks, and Kajabi documents webhooks as Growth and Pro only.
What Zapier buys you over plain webhooks: no code, visual field mapping, easy multi-step flows (tag in Kit, then add to a Google Sheet, then ping Slack), and filters so you only fire on the offers you care about.
The 400-error gotcha
When testing inbound Zaps that grant a Kajabi offer, you may hit a 400 error. The usual cause is that the offer has already been granted to that contact, and Kajabi will not grant the same offer twice. Generate fresh test data rather than re-firing the same record.
Common problems (and what is actually causing them)
Duplicate confirmation emails
Double opt-in is on in both Kajabi and Kit. Disable it on the Kajabi form.
Webhooks queue or fire late during a launch
Under heavy traffic, webhook delivery can lay and delay the triggering. Build your sequences so a few minutes’ delay does not break the experience, and avoid time-critical logic that assumes instant delivery.
Tags from the native app are not showing up in Kit
Confirm the contact actually has access to the product in Kajabi, since product tags follow the kajabi_[product_name] pattern and only apply to contacts with access.
New mappings apply to future syncs, so you may need to update a contact in Kajabi to trigger a fresh sync.
Zapier throws a 400 when granting an offer
The offer is already granted to that contact. Kajabi will not grant the same offer twice; use fresh test data.
Kajabi & Kit Integration FAQ
1) Is ConvertKit the same as Kit?
Yes. ConvertKit rebranded to Kit in 2024.
It is the same product and company. Older Kajabi menus may still say ConvertKit while newer Kit docs say Kit.
2) Does Kajabi integrate with ConvertKit (Kit)?
Yes, in three different ways: a free native form connector that works on any plan, outbound webhooks (Growth and Pro), Zapier (effectively Growth and Pro),
3) Do I need Kajabi Pro to connect Kit?
No. The native form connector works on any plan.
You only need Pro (or the $25/month Public API add-on on Basic or Growth) for Kit’s deep native app. Webhooks and Zapier need Growth or Pro but not the API add-on.
4) Can I connect Kajabi and Kit without the API?
Yes. The native form connector and webhooks both work without the Public API. Only Kit’s native Kajabi app requires it.
5) Why isn’t my Kajabi tag showing up in Kit?
Most often the contact does not actually have access to the product in Kajabi, since product tags only apply to contacts with access.
New tag mappings also only apply to future syncs, so update the contact in Kajabi to force a fresh sync.
6) Can I use Zapier instead of the native integration?
Yes, and it is a good no-code option, but in practice it needs Growth or Pro because its Kajabi triggers rely on webhooks.
It is more flexible across other apps but does not replicate the native app’s two-way student and tag sync.
