Skip to content
Campaign Monitor logoConvertKit logo

Connect Campaign Monitor to ConvertKit

Move data between Campaign Monitor 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.

Campaign Monitor triggers
3
Campaign Monitor actions
4
ConvertKit triggers
12
ConvertKit actions
36

Automation ideas

What you can build with Campaign Monitor and ConvertKit

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

  • New Subscriber Added in Campaign Monitor creates Get Subscriber By Id in ConvertKit

    Triggered when a new subscriber is added to a list.

  • Tag added to subscriber in ConvertKit creates Add Subscriber in Campaign Monitor

    Trigger when a tag is added to a subscriber

  • New Subscriber Added in Campaign Monitor creates Get Subscriber By Email in ConvertKit

    Triggered when a new subscriber is added to a list.

  • Tag added to subscriber in ConvertKit creates Update Subscriber in Campaign Monitor

    Trigger when a tag is added to a subscriber

  • New Subscriber Added in Campaign Monitor creates List Subscribers in ConvertKit

    Triggered when a new subscriber is added to a list.

  • Tag added to subscriber in ConvertKit creates Unsubscribe Subscriber in Campaign Monitor

    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 Campaign Monitor 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.