Customer.io Make integrationAutomate Customer.io with Make.
Your signups, purchases and cancellations live in other tools. The Customer.io Make integration carries them over. Make offers 6 action modules for Customer.io. This guide shows what each one does, how to connect your account and how to build a first scenario that feeds your campaigns.
Verified Trustpilot reviews · AI, automation & growth agency
What can the Customer.io Make integration do for you?
The Customer.io Make integration lets Make write into your Customer.io account: add or update a person, record an event, drop people into a manual segment, suppress or delete a profile. It has no trigger, so a scenario (the automation you build in Make) always starts in another app or on a schedule, then hands the data to Customer.io.
Every trial signup becomes a Customer.io profile. A form tool or your product database opens the scenario, Create or Update a Customer writes the person, and your onboarding campaign has someone to talk to. No CSV export, no copy and paste.
Purchases turn into events your campaigns can react to. When your billing tool records a payment, Track a Customer Event logs it on the right profile. A win-back or upsell message can then key off that event inside Customer.io.
Your sales team hand-picks who gets a message. A row marked in a spreadsheet can feed Add People to Segment, so a manual segment stays in sync with a list someone curates by hand.
What Make does not do here: react to something that happens inside Customer.io. The app has no trigger module in Make, so Customer.io is always the destination of the flow. If you need an endpoint the six modules skip, Make an API Call reaches the rest of the Customer.io API with the same connection.
Customer.io also has an n8n node, covered on the Customer.io n8n integration page, and the n8n vs Make comparison helps you pick a tool. New to scenarios? The Make training starts from zero.
How do you connect Customer.io to Make?
- 01
Add a Customer.io module
In your scenario, add any Customer.io module, for example Create or Update a Customer. Make asks for a connection, meaning your Customer.io account linked to Make once. Click Create a connection.
- 02
Name the connection
Naming is optional, but a clear label pays off. If you run a test account and a production account, a name like "Customer.io production" stops you from sending real events to the wrong place later.
- 03
Authorize and save
Follow what Make displays: either approve access on the Customer.io page that opens, or paste the key Customer.io gives you. Then click Save. The connection now works for all six Customer.io modules.
Your first scenario: new signup, new profile, first event
GoalWhen someone signs up through your form tool, Make creates their Customer.io profile and records a signup event on it.
- 01
Start from your form tool
From the Scenarios page, create a new scenario and click the + to add the first module. Pick the app that collects signups and its module that returns new submissions. That module opens the flow.
- 02
Add Create or Update a Customer
Click the + to the right of the first module, search for Customer.io and choose Create or Update a Customer. Click Create a connection if you have not linked your account yet.
- 03
Map the signup data
Fill the module fields by picking values from the form module: Make shows the data it received, so you click the email or name instead of typing it. Each submission is one bundle, one item passing through.
- 04
Record the event
Add Track a Customer Event after it and map the same person. If the module asks for an event name, reuse one your team already knows, so your campaigns can spot it.
- 05
Test with Run once
Submit a test entry in your form, then click Run once. Make runs the scenario one time and shows the bundles each module received. Check the profile and the event in Customer.io.
- 06
Schedule and switch on
Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. On the Free plan, 15 minutes is also the shortest interval between two scheduled runs.
The 6 Customer.io modules in Make
Customer.io gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.
Add People to Segment
ActionIn Make“Adds people to a manual segment”
Puts people into a manual segment of Customer.io, a group you fill yourself. Your campaigns can then target exactly the people you chose.
Create or Update a Customer
ActionIn Make“Creates a new customer or updates the existing one.”
Writes a person into Customer.io: if the profile does not exist yet it is created, if it exists it is updated. One module covers both cases, so you do not need to check first.
Delete a Customer
ActionIn Make“Deletes a customer and all their information from Customer.io.”
Removes a person from Customer.io along with everything stored about them. Use it when the profile must disappear, not just stop receiving messages.
Make an API Call
ActionIn Make“Performs an arbitrary authorized API call.”
Calls any endpoint of the Customer.io API from your scenario, reusing the connection you already created. It is the fallback when the five named modules do not cover what you need.
Suppress a Customer
ActionIn Make“Suppresses a customer. In addition to suppressing, the customer will also be deleted automatically.”
Suppresses a person in Customer.io, and the profile is also deleted automatically as part of the same action. Think of it as a stronger version of a delete, not a pause button.
Track a Customer Event
ActionIn Make“Tracks a new customer event.”
Logs an event on a person's profile in Customer.io, such as a payment, a canceled plan or a finished onboarding step. Campaigns inside Customer.io can react to those events.
Need help automating Customer.io with Make?
A person reads every message.
