Customer.io integration: an AI agent for events and reports

Letaido's Customer.io integration lets an AI agent send people and events from Stripe and Calendly, and report email results in Slack or Sheets.

Get Letaido

Best Customer.io integration jobs to start with

Events that start your automations, weekly results and newsletter drafts. Open one to watch it run.

On a new Stripe customer

New Stripe customers added to Customer.io

When a customer is created in Stripe, add or update them in Customer.io with name and Stripe ID, and send a customer_created event.

On a Calendly demo booking

Calendly demo bookings sent to Customer.io

When someone books a Calendly demo, add or update them in Customer.io and send a demo_booked event with the meeting time, for reminders and follow-up.

Every Friday at 4pm

Weekly Customer.io automation results in Slack

Every Friday afternoon, post each active Customer.io automation's emails delivered, open rate, click rate and conversions for the week to #lifecycle.

On a Stripe cancellation

Canceled Stripe subscriptions start a Customer.io win-back

When a Stripe subscription is canceled, mark the person in Customer.io and send a subscription_canceled event with the plan and reason, for your win-back automation.

When you ask

Why a customer missed your email

Ask about one person and get a plain answer from Customer.io: unsubscribed, opted out, suppressed for bounces or spam, or what was sent recently.

Customer.io integration options, compared

Six ways to connect Customer.io to the rest of your stack.

Option	Set up by asking	Works across your apps	Runs on its own	No code	Connects thousands of apps
Letaido AI agent	Yes	Yes	Yes	Yes	No
Customer.io integration directory	No	Partly	Yes	Yes	No
Customer.io journeys and agent routines	Partly	No	Yes	Yes	No
Zapier and similar	Yes	Yes	Yes	Yes	Yes
Customer.io APIs	No	Partly	Partly	No	Partly
Customer.io MCP server, ChatGPT and Claude	Yes	Partly	No	Yes	No

Read the full comparison

Option	How it works	Best for	Watch out for
Letaido AI agent	You describe the job. The agent works across Customer.io and your other apps, on a schedule, another app's event or when you ask.	Lifecycle work that crosses apps: Stripe and Calendly events that start automations, weekly results in Slack or Sheets, newsletter drafts.	A focused catalog, not thousands of apps. Customer.io itself can't start a job yet. Adding people and events also needs your Track API keys.
Customer.io integration directory	Ready-made data-in sources and data-out destinations, such as Salesforce, HubSpot, Segment, Snowflake, Amplitude and Google Ads, set up under Integrations in Customer.io.	Syncing CRM, warehouse and product data in, and sending audiences and message data out.	Each integration does one set job between Customer.io and that tool. Premium data integrations need the Premium or Enterprise plan.
Customer.io journeys and agent routines	Automations built in the visual workflow builder send messages from events and segments. Customer.io's own agent can also run routines: scheduled checks it sets up when you chat with it.	Messaging inside Customer.io, plus recurring read-only checks like a broadcast recap.	Routines run in safe mode: they read and analyze, then email a summary, and can't change anything. They run weekly on Essentials and daily on Premium.
Zapier and similar	Zapier's Customer.io app lists three actions: create or update a person, create an event and create an anonymous event. Zapier Copilot builds a workflow from a prompt.	Fixed handoffs into Customer.io, like a form entry becoming a person.	Data goes one way, into Customer.io. It lists no actions for reading metrics or building newsletters. Check what Copilot sets up.
Customer.io APIs	The Track and Pipelines APIs send people and events in. The App API, with an App API key, sends messages and reads data out.	In-house apps with exact needs, like transactional emails from your product.	Needs developers. The App API allows 10 requests a second and one API-triggered broadcast every 10 seconds.
Customer.io MCP server, ChatGPT and Claude	An account admin turns on MCP under Settings, AI. Each user then connects ChatGPT, Claude, Cursor or another MCP client with their own Customer.io login and picks scopes such as read or write.	Asking questions about your workspace and drafting automations, segments and emails in a chat.	Runs when you chat. By default a connection only gets the read scope, and deleting people or editing live data needs an admin setting.

How the Customer.io integration works

Connect Customer.io once. After that, you describe each job in plain English.

1Paste a Customer.io App API key
2Ask for a job in a chat, or start from an example above
3Approve the first run
Allow all read operations once per app; approve each kind of write once.
4Watch the first run in the chat
Save it to run on a schedule or another app's event.

How a Customer.io job starts

A schedule, you asking, or a Stripe or Calendly event starts the job.

On a scheduleEvery Monday morning or Friday afternoon, like the weekly newsletter stats.
When you askType the job in a chat, like turning a Google Doc into a newsletter draft, and it runs once.

Setup details

Create an App API key

In Customer.io, open Account Settings, then API Credentials, and create an App API key for your workspace. You need to be an account admin or have the Manage API credentials permission. The key is shown only once.

Copy your Track API keys

Jobs that add people or send events also need the workspace's Track API site ID and API key, from the same page.

Paste them into Letaido

Pick your account region, US or EU, so the agent talks to the right Customer.io data center.

Watch the first run

Allow all read operations once per app; approve each kind of write once. Then save it to repeat.

Every Customer.io action the agent can take

214 actions in 12 groups, from people and events to newsletters and Design Studio.

ReadsWrites

Related integrations

Frequently asked

How do I connect Customer.io to Letaido? +

In Customer.io, open Account Settings, then API Credentials, create an App API key and paste it into Letaido with your region, US or EU. Add the workspace's Track API site ID and key if your jobs add people or send events. You need to be an account admin or have the Manage API credentials permission.

Can a change in Customer.io start a job? +

Not yet. Customer.io jobs start on a schedule, when something happens in another app, like a new Stripe customer or a Calendly booking, or when you ask in a chat.

Will new Stripe customers or Calendly bookings start my Customer.io automations? +

Yes. With your Track API keys on the connection, the agent adds or updates people and sends events like customer_created or demo_booked. Any automation you built in Customer.io on that event can then start.

Is there a Customer.io MCP server? +

Yes. Once an account admin turns it on under Settings, AI, each user connects ChatGPT, Claude, Cursor or another MCP client with their own login and picks scopes such as read or write. Letaido is not an MCP server: it has its own Customer.io connector and runs whole jobs on a schedule, another app's event or when you ask.

How is Letaido different from Customer.io's agent routines? +

Routines are scheduled checks by Customer.io's own agent. They only read and analyze, then email you a summary. Letaido jobs work across apps: they post results to Slack or Sheets, and add people and events from Stripe or Calendly.

Does it send messages to my customers? +

It can send transactional messages, newsletters and API-triggered broadcasts when a job asks for it. The jobs above send nothing themselves: their events can start your own Customer.io automations, which do send, and the newsletter job saves a draft for you to review.

What do I approve before it changes Customer.io? +

Allow all read operations once per app; approve each kind of write once.

Give an AI agent your Customer.io workspace

Connect Customer.io, then ask for a job like "Add every new Stripe customer to Customer.io and start our onboarding". Leta gets it done the moment something happens, or the moment you ask.