Customer.io Zapier integrationAutomate Customer.io with Zapier.
The Customer.io Zapier integration gives you 3 actions, and no trigger or search. It works one way: other apps feed people and events into Customer.io, and your campaigns react. Here is what each action does, what it costs and where a Zap tends to go wrong.
Verified Trustpilot reviews · AI, automation & growth agency
What the Customer.io Zapier integration actually does
It pushes data into Customer.io from your other tools. A signup form, a payment tool or a spreadsheet hands over a person or an event, and Customer.io takes it from there: the messages, segments and campaigns you already set up react to what arrives.
Three outcomes cover most real uses. Profiles that stay current: Create or Update a Person adds a new contact or refreshes an existing one, so your segments see the latest plan, role or company. Campaigns started by real behavior: Create Event records something a known person did elsewhere, like a paid invoice or a booked demo, and any campaign listening for that event can fire. Visitors tracked before they sign up: Create Anonymous Event logs activity for someone you cannot name yet, tied to an anonymous ID.
Now what it does not do. Nothing flows out of Customer.io: there is no trigger, so a Zap cannot start when someone opens an email, joins a segment or unsubscribes. There is no search either, so a Zap cannot look up a person before writing. And no action sends a message directly; Customer.io does the sending once the data is in. If you need data coming back out, look at the Customer.io n8n integration or the Customer.io Make integration before you build.
Good news on cost: Customer.io is not a premium app on Zapier, so a two-step Zap runs on the free plan.
Zapier vocabulary in one minute
Seven words you will meet in the editor. Read them once and the rest of the page gets easy.
- Zap
- The automation you build: one starting event, then one or more steps that run each time that event happens.
- Trigger
- The event that starts the Zap. With Customer.io it always comes from another app, such as a new form entry.
- Action
- What the Zap does once it starts: here, adding a person or recording an event in Customer.io.
- Task
- The unit Zapier bills. Each action that completes successfully counts as one task on your plan.
- Polling vs instant
- A polling trigger is checked on a timer. An instant trigger is pushed by the app the moment the event happens.
- Filter
- A step that lets the Zap continue only when the data meets your condition, and stops it quietly otherwise.
- Connection
- Your Customer.io account linked to Zapier once, then reused by every Customer.io step in every Zap.
What a Customer.io Zap really costs
The trigger is free. Zapier bills each Customer.io action that succeeds, one task per action.
- Free plan100 tasks a month
- Steps per Zap on Free2 (trigger + action)
- Customer.io appNot premium
- Customer.io triggersNone, start from another app
A Zap that creates a person and then records an event uses two tasks every run. A failed action is not counted against your plan. The free plan includes 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger, one action. Adding a filter or a second Customer.io action turns it into a multi-step Zap that needs a paid plan. Since the trigger always comes from another app, the interval grid below depends on that app's trigger, not on Customer.io.
Connect Customer.io to Zapier in three steps
- 01
Start from your Zapier apps
In Zapier, open Apps and click + Add connection. In the dialog, search for Customer.io and select it. Use an account that can write to the workspace where your people and campaigns live.
- 02
Sign in to Customer.io
Click Add connection. Customer.io opens in a new tab: sign in there. If the workspace belongs to a colleague or another team, ask for write access first, or the actions will have nowhere to land.
- 03
Approve, then reuse
Grant Zapier access to the account. The connection appears on your Apps page and every Customer.io step can select it, so you only do this once per account.
Your first Customer.io Zap
GoalEvery paying customer becomes an up-to-date person in Customer.io, with a purchase event your onboarding campaign can listen for.
- 01
Pick the starting app
Start a new Zap and choose the app where the event happens, here your payment tool. Customer.io has no trigger, so the Zap always starts elsewhere.
- 02
Test that trigger
Run the test. Zapier fetches the three most recent items from the connected account, so you map the next steps on a real payment, with a real email.
- 03
Filter out the noise
Add a Filter step to keep only real payments and skip test charges or refunds. This makes the Zap multi-step, which means a paid plan.
- 04
Write to Customer.io
Add Create or Update a Person and map the Id from the payment, then Create Event with the same Id and an event name your campaign already uses.
- 05
Test and publish
Test each step, check the person and the event in Customer.io, then click Publish. Only payments made after this point go through.
Customer.io actions
Customer.io gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create or Update a Person
ActionIn Zapier“Creates a new person. If the person already exists, it will be updated.”
Adds someone to your Customer.io workspace, or refreshes their profile if that Id already exists. One step covers both cases, so you never need to check first.
Create Anonymous Event
ActionIn Zapier“Creates an anonymous event.”
Logs activity for a visitor you cannot identify yet, stored against an anonymous ID instead of a person. Handy for capturing intent before a signup happens.
Create Event
ActionIn Zapier“Creates an event.”
Records an action a known person took outside Customer.io, under the event name you choose. Campaigns and segments built on that name can use it.
When the Customer.io Zap breaks
Zapier links one help article to this app, a getting-started guide for Customer.io on Zapier, and lists no Customer.io-specific limit.
The failures you will meet come from how Zapier works overall and from how Customer.io identifies people. The four below are the ones to plan for. When one hits, the Zapier troubleshooting guide walks through the fixes step by step.
Past contacts never arrive
A Zap only handles what happens after you publish it. People who signed up before stay out of Customer.io until you import them separately.One customer, two kinds of Id
The update only applies when the Id matches an existing person. Mix user IDs in one Zap and emails in another, and the same customer may not be matched. Keep one Id convention everywhere.A bulk import gets paused
If the starting app suddenly returns a huge batch after an import or a migration, Zapier's flood protection can hold those runs back.Events that trigger nothing
Create Event works, but no campaign reacts. The event name in the Zap differs from the one your campaign listens for.
Need help automating Customer.io with Zapier?
A person reads every message.
