Skip to content
customer.io logoDrip logo

Connect customer.io to Drip

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

customer.io triggers
1
customer.io actions
3
Drip triggers
2
Drip actions
4

Automation ideas

What you can build with customer.io and Drip

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

  • New Reporting Event in customer.io creates Apply a tag to subscriber in Drip

    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 in Drip creates Create Event in customer.io

    Triggers when a subscriber is created in your Drip account.

  • New Reporting Event in customer.io creates Add a subscriber to a campaign in Drip

    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 in Drip creates Track Custom API Call in customer.io

    Triggers when a subscriber is created in your Drip account.

  • New Reporting Event in customer.io creates Create or Update Subscriber in Drip

    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 in Drip creates App Custom API Call in customer.io

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