A creator who writes in one tool and sends in the other
A writer keeps paid-subscriber emails in MailerLite and public newsletters in Kit. A buyer gets both the Kit tag and the MailerLite group, and a refund takes both away.
Native integration
Kit (ConvertKit) + MailerLite integration
A Kit tag and a MailerLite group for the same buyer, added on purchase and removed together on a full refund.
No credit card required. No coding required.
Kit (ConvertKit)
MailerLiteDoes Kit (ConvertKit) integrate with MailerLite?
Plandalf does not sync Kit (ConvertKit) with MailerLite, but both are native, so one sequence can tag the buyer in Kit and add them to a MailerLite group. The Remove access on refund template then handles both in a single sequence.
What moves between Kit (ConvertKit) and MailerLite
| Event | From and to | Through | What happens |
|---|---|---|---|
| Checkout completed | Plandalf → Kit | Native step | Tag Subscriber with a Customer tag, then Add Subscriber to Sequence for onboarding. |
| Checkout completed | Plandalf → MailerLite | Native step | Find or Create Subscriber, then Add Subscriber to Group. Run the first step's test so the group step can read subscriber_id. |
| Invoice refunded | Plandalf → Kit | Native step | Remove Tag from Subscriber in the template, with Email Address already set to {{trigger.customer_email}}. |
| Invoice refunded | Plandalf → MailerLite | Native step | Remove Subscriber from Group in the same sequence. It looks the subscriber up by email and leaves them in your MailerLite account. |
| Subscriber joined form | Kit → MailerLite | Native step | A Kit form trigger starts a sequence that adds the person to a MailerLite group, which can start a MailerLite automation. |
One refund sequence that cleans up Kit and MailerLite
Connect both apps before you add the template, because it only adds steps for apps already connected.
Connect Kit and MailerLite
In Automation, Marketplace, connect Kit with a V4 key and MailerLite with a token from the current MailerLite.
Build the purchase sequence
Create the sequence on Plandalf, Checkout Completed. Add Kit, Tag Subscriber, then MailerLite, Find or Create Subscriber and Add Subscriber to Group.
Add the refund template
Under Automation, Templates, add Remove access on refund for the same checkout. Plandalf opens a sequence with a step for each connected app.
Finish both steps
Pick the Kit tag in Remove Tag from Subscriber and the group in Remove Subscriber from Group. Delete any other app's step you do not need.
Turn on and rehearse
Leave Full refunds only on. Run on test purchases lets a test card exercise the purchase path, but refunds of test purchases are skipped too, so check the refund sequence against the Events view with a real small refund of your own.
What sellers do with Kit (ConvertKit) and MailerLite
Trial offers with a short refund window
A paid trial often ends in a refund. The one template removes access in both tools, so a refunded person stops receiving customer-only emails from either.
Limits and gotchas
- The refund trigger runs on a refund that succeeds in Stripe. A PayPal refund does not start it, so remove access by hand for those.
- Both removal steps are skipped, not failed, when the buyer has no tag or group, which can hide a typo in the email variable. Check the Events view.
- The template only adds steps for apps connected when you add it, so connect MailerLite and Kit first.
- Kit purchases are not recorded in its purchase history, and MailerLite takes no order data through these steps.
- MailerLite Classic does not connect, and Kit needs the V4 key.
Kit (ConvertKit) and MailerLite: common questions
- Does Kit integrate with MailerLite?
- Plandalf does not sync them. Both have native steps, so one sequence can write the buyer to each and one refund template can take them back out.
- How do I connect ConvertKit to MailerLite?
- Connect both in Plandalf and build a sequence that runs Kit and MailerLite steps from one trigger. The recipe on this page covers the order.
- How do I migrate from Kit to MailerLite?
- Plandalf keeps new buyers going into both while you rebuild. Import the existing subscribers using MailerLite's own tools.
- Why does the group step need a subscriber ID?
- MailerLite's group and field steps work on an ID. Find or Create Subscriber returns it, so run that step first.
Guides for this pair
- Plandalf with Kit (ConvertKit)
- Plandalf with MailerLite
- Kit setup guide
- MailerLite setup guide
- Remove access on refund
More from Kit (ConvertKit) and MailerLite
- Kit (ConvertKit) + ZapierKit steps are native in Plandalf. Zapier covers Kit events and purchase records that the native steps leave out.
- Flodesk + Kit (ConvertKit)Flodesk segments can start Kit tags and sequences through a Plandalf catch URL, and a checkout can write the buyer to both.
- Kajabi + Kit (ConvertKit)One paid checkout grants the Kajabi offer and tags the buyer in Kit, from a single Plandalf sequence.
- Shopify + MailerLiteMailerLite's Shopify app covers the store. A Plandalf offer opened from a Shopify page puts its own buyers in a MailerLite group with native steps.
- Stripe + MailerLiteA paid Plandalf checkout puts the buyer into a MailerLite group, and a refund in Stripe takes them back out, so the group matches who actually paid.
- Webflow + MailerLiteWebflow hosts the buy button, Plandalf takes payment, and MailerLite gets each buyer in the group that starts your emails.
Checked October 26, 2026 against Plandalf's own setup guides.