A creator opening an online shop
A newsletter writer on Kit starts selling prints through a Plandalf checkout. Kit tags the buyer for the customer segment, while Klaviyo holds shop profiles that drive order flows.
Native on one side, webhook on the other
Klaviyo + Kit (ConvertKit) integration
Kit gets native Plandalf steps, Klaviyo gets a webhook call to its API, and one checkout can feed both.
No credit card required. No coding required.
Klaviyo
Kit (ConvertKit)Does Klaviyo integrate with Kit (ConvertKit)?
Plandalf does not sync Klaviyo with Kit (ConvertKit). Kit has native steps, while Klaviyo is reached with Send Webhook against its API. One sequence can do both, a Kit tag or form can start a sequence, and a Klaviyo flow webhook can post to a Plandalf catch URL.
What moves between Klaviyo and Kit (ConvertKit)
| Event | From and to | Through | What happens |
|---|---|---|---|
| Checkout completed | Plandalf → Kit | Native step | Tag Subscriber creates the subscriber if Kit lacks them. Add Subscriber to Sequence then starts the onboarding emails, provided the Kit sequence is active. |
| Checkout completed | Plandalf → Klaviyo | Webhook | A Send Webhook step posts a profile to Klaviyo's profile import, with a Klaviyo-API-Key authorization header and a revision header. |
| Tag added | Kit → Klaviyo | Webhook | Plandalf adds the Kit webhook when you save the trigger. The sequence's Send Webhook step then writes the tagged subscriber into Klaviyo, so the tag name can become a profile property. |
| Flow webhook | Klaviyo → Kit | Webhook | A Klaviyo flow's Webhook action posts JSON to a Plandalf catch URL. The sequence runs a native Kit step, such as Add Subscriber to Form, for the email it receives. |
| Invoice refunded | Plandalf → Kit | Native step | Remove Tag from Subscriber takes the Kit tag back. Nothing is removed in Klaviyo unless you add a webhook call for it. |
Tag in Kit, create a profile in Klaviyo
You need a Kit V4 API key and a Klaviyo private API key.
Connect Kit
In Automation, Marketplace, connect Kit under Available now. Paste a V4 key from Settings, then Developer, not the legacy V3 key.
Start the sequence
Create it under My Sequences with Plandalf and Checkout Completed, limit it to your offer, and choose a sample checkout on the Test tab.
Tag and enrol in Kit
Add Kit, Tag Subscriber with the email and a tag such as Customer. Then add Add Subscriber to Sequence with your onboarding sequence.
Add the Klaviyo profile
Add Send Webhook, POST to Klaviyo's profile import. Set the three headers and a JSON:API payload that holds the email and first name from the trigger.
Add a Klaviyo-to-Kit path if you need it
Create a second sequence with the Webhook Trigger, paste its URL into a Klaviyo flow Webhook action, and run a native Kit step for the email in the sample it captures.
Test
Switch on Run on test purchases, buy through the test link with your own email, and check the Kit subscriber and the Klaviyo profile before switching it off.
What sellers do with Klaviyo and Kit (ConvertKit)
Klaviyo audience, Kit course delivery
A Klaviyo flow posts to a catch URL when a profile joins a course waitlist, and the sequence adds that person to a Kit form so the course emails start.
Limits and gotchas
- Purchases do not appear in Kit's purchase history because Plandalf connects with an API key. Use a tag or custom field to record what was bought.
- Klaviyo's profile import does not subscribe the profile to marketing. Consent needs its own subscribe request.
- Klaviyo flow webhooks need two-step authentication and a Manager, Admin or Owner role, only send POST with JSON, and cover only events that can trigger a flow.
- Kit allows 120 requests a minute per key and Klaviyo has its own limits, so a large burst of buyers can slow one side.
- Plandalf has no step that unsubscribes someone in Kit, so an unsubscribe in Klaviyo has no automatic counterpart.
Klaviyo and Kit (ConvertKit): common questions
- Does Klaviyo integrate with Kit?
- Plandalf does not connect the two. It writes buyers to Kit with native steps and to Klaviyo with a webhook call, and either tool can start a sequence. Each vendor's own integrations list covers direct links.
- How do I connect Klaviyo to ConvertKit?
- Connect Kit in Plandalf, then build a sequence on Checkout Completed with Kit steps and a Send Webhook step to Klaviyo's profile import. The recipe above has the details.
- Will a Kit tag appear in Klaviyo?
- Only if a sequence sends it. Use the Kit Tag Added trigger and a Send Webhook step that writes the tag name into a Klaviyo profile property.
- Is Kit the same as ConvertKit?
- Yes. ConvertKit became Kit, and Plandalf's pages still use both names for the same app.
Guides for this pair
Start your 14-day free trialMore from Klaviyo and Kit (ConvertKit)
- HubSpot + KlaviyoPlandalf sits beside HubSpot and Klaviyo: one checkout writes the buyer to both by webhook, and each can start a Plandalf sequence.
- Mailchimp + KlaviyoA Plandalf checkout writes the buyer to Mailchimp natively and to Klaviyo through its API, so both lists fill while you decide which one wins.
- Next.js + KlaviyoYour Next.js app owns the page, Plandalf owns checkout, and the paid order lands in Klaviyo as an event that can start a flow.
- Teachable + Kit (ConvertKit)When a course checkout is paid, one sequence enrols the student in Teachable and tags the same person in Kit.
- Thinkific + Kit (ConvertKit)A paid Plandalf checkout enrols the student in a Thinkific course or bundle and tags them in Kit.
- Vue + Kit (ConvertKit)A Vue 3 component opens the checkout through the browser SDK, and Kit tags and emails the buyer from a paid order.
Checked October 26, 2026 against Plandalf's own setup guides and the vendor documentation: Klaviyo API: create or update profile (profile import), Klaviyo: how to add a webhook action to a flow.