Skip to content
MailerLite logoConvertKit logo

Connect MailerLite to ConvertKit

Move data between MailerLite and ConvertKit the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

MailerLite triggers
4
MailerLite actions
11
ConvertKit triggers
12
ConvertKit actions
35

Automation ideas

What you can build with MailerLite and ConvertKit

A few flows teams run between MailerLite and ConvertKit. Use one as a starting point, or build your own from scratch.

  • Subscriber Created in MailerLite creates Get Subscriber By Id in ConvertKit

    Triggers when a subscriber was created on your mailing list.

  • Tag added to subscriber in ConvertKit creates Add Subscriber to a Group in MailerLite

    Trigger when a tag is added to a subscriber

  • Subscriber Created in MailerLite creates Get Subscriber By Email in ConvertKit

    Triggers when a subscriber was created on your mailing list.

  • Tag added to subscriber in ConvertKit creates Add or Update subscriber in MailerLite

    Trigger when a tag is added to a subscriber

  • Subscriber Created in MailerLite creates List Subscribers in ConvertKit

    Triggers when a subscriber was created on your mailing list.

  • Tag added to subscriber in ConvertKit creates Find a Subscriber in MailerLite

    Trigger when a tag is added to a subscriber

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in MailerLite and acts in ConvertKit, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.