Skip to content
Drip logoCampaign Monitor logo

Connect Drip to Campaign Monitor

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

Drip triggers
10
Drip actions
33
Campaign Monitor triggers
3
Campaign Monitor actions
4

Automation ideas

What you can build with Drip and Campaign Monitor

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

  • New Subscriber in Drip creates Add Subscriber in Campaign Monitor

    Triggers when a subscriber is created in your Drip account.

  • New Subscriber Added in Campaign Monitor creates Apply a tag to subscriber in Drip

    Triggered when a new subscriber is added to a list.

  • New Subscriber in Drip creates Update Subscriber in Campaign Monitor

    Triggers when a subscriber is created in your Drip account.

  • New Subscriber Added in Campaign Monitor creates Add a subscriber to a campaign in Drip

    Triggered when a new subscriber is added to a list.

  • New Subscriber in Drip creates Unsubscribe Subscriber in Campaign Monitor

    Triggers when a subscriber is created in your Drip account.

  • New Subscriber Added in Campaign Monitor creates Create or Update Subscriber in Drip

    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 Drip 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.