Skip to content
customer.io logoSendr logo

Connect customer.io to Sendr

Move data between customer.io and Sendr 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
Sendr triggers
4
Sendr actions
19

Automation ideas

What you can build with customer.io and Sendr

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

  • New Reporting Event in customer.io creates Get Account Info in Sendr

    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 Page Render in Sendr creates Create Event in customer.io

    Triggers when a new Sendr Page is rendered.

  • New Reporting Event in customer.io creates List Sheets in Sendr

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

    Triggers when a new Sendr Page is rendered.

  • New Reporting Event in customer.io creates Get Sheet in Sendr

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

    Triggers when a new Sendr Page is rendered.

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