Skip to content
customer.io logoCampaign Monitor logo

Connect customer.io to Campaign Monitor

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

customer.io triggers
1
customer.io actions
3
Campaign Monitor triggers
3
Campaign Monitor actions
4

Automation ideas

What you can build with customer.io and Campaign Monitor

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

  • New Reporting Event in customer.io creates Add Subscriber in Campaign Monitor

    Fires on a Customer.io reporting-webhook event (delivered, bounced, clicked, …). Subscribe to only the event types you need, and optionally match a single campaign, action, or recipient domain so unrelated events never start a run.

  • New Subscriber Added in Campaign Monitor creates Create Event in customer.io

    Triggered when a new subscriber is added to a list.

  • New Reporting Event in customer.io creates Update Subscriber in Campaign Monitor

    Fires on a Customer.io reporting-webhook event (delivered, bounced, clicked, …). Subscribe to only the event types you need, and optionally match a single campaign, action, or recipient domain so unrelated events never start a run.

  • New Subscriber Added in Campaign Monitor creates Track Custom API Call in customer.io

    Triggered when a new subscriber is added to a list.

  • New Reporting Event in customer.io creates Unsubscribe Subscriber in Campaign Monitor

    Fires on a Customer.io reporting-webhook event (delivered, bounced, clicked, …). Subscribe to only the event types you need, and optionally match a single campaign, action, or recipient domain so unrelated events never start a run.

  • New Subscriber Added in Campaign Monitor creates App Custom API Call in customer.io

    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 customer.io 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.