Skip to content
Campaign Monitor logoDrip logo

Connect Campaign Monitor to Drip

Move data between Campaign Monitor and Drip 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
Drip triggers
10
Drip actions
33

Automation ideas

What you can build with Campaign Monitor and Drip

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

  • 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 Add 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 Update 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.

  • New Subscriber in Drip creates Unsubscribe Subscriber in Campaign Monitor

    Triggers when a subscriber is created in your Drip account.

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