Skip to content
ConvertKit logoCampaign Monitor logo

Connect ConvertKit to Campaign Monitor

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

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

Automation ideas

What you can build with ConvertKit and Campaign Monitor

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

  • 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 Id 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 Get Subscriber By Email 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

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

    Triggered when a new subscriber is added to a list.

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 ConvertKit and acts in Campaign Monitor, 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.