Integration · Marketing
AI agents for Customer.io
Send transactional emails, trigger API broadcasts, and look up and search people in a Customer.io workspace, in the US or EU region, with an App API key.
- Actions
- 5
- Read
- 3
- Write
- 2
Actions
What your agents can do in Customer.io
5 actions. Each one is a tool your agents can call and a step your workflows can run.
Read 3
Look things up. Nothing changes.
Get a person's attributes
Reads one person's profile by customer ID, email or cio_id: identifiers, every attribute, when attributes changed, and whether they unsubscribed.
Find people by email
Finds the people in the workspace with an email address, with each one's id, email and cio_id.
Search people
Finds people who are in a segment and/or have an attribute (any value, or exactly value); give at least one of segment_id and attribute.
Write 2
Create, change or send.
Send a transactional email
Sends one transactional email from a transactional message template (by its numeric ID or trigger name) to one address, filling the template's Liquid placeholders from message_data.
Trigger an API broadcastDeletes data
Sends an API-triggered broadcast (set up in Customer.io) to its default audience, or only to the given emails or customer IDs, who must already be in the workspace.
A person can approve first
Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.
Connection
How it connects
Connect it once in the console, then give it to the agents and workflows that need it.
Paste an API key from your Customer.io account.
What you enter
- App API key
Settings
- Region
Kept safe
- Credentials are stored encrypted with your organization's own keys.
- They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
- Calls go only to the tool's own servers.
Ideas
Ideas to start with
Starting points made only from the actions above. Mix them with any other tool your agents can use.
- 01
Ask about your Customer.io data
Ask a question in plain words. The agent can get a person's attributes, find people by email or search people in Customer.io, then answers with what it found.
- 02
Let an agent update Customer.io
Have the agent send a transactional email or trigger an API broadcast in Customer.io as part of a larger task. Turn on approval and a person signs off on each change first.
- 03
Share what it finds in Slack
Give one agent Customer.io and Slack: it can get a person's attributes in Customer.io and post a summary to a Slack channel in the same run.
Works well with
More Marketing tools
- Mailchimp2 actionsAdd people to your Mailchimp audiences or update them, with their merge fields and tags, and look up your audiences.
- Klaviyo3 actionsCreate or update Klaviyo profiles, subscribe people to email marketing on a list, and record events that start flows.
- ActiveCampaign4 actionsCreate or update ActiveCampaign contacts, find them by email, and add them to lists and tags.
- LinkedIn2 actionsPublish text posts on a member's LinkedIn profile and read the signed-in member's name and email, after the member signs in with LinkedIn.
- X4 actionsPost and delete on X as the signed-in account, read an account's recent posts, and look up X users by username.
- YouTube4 actionsRead a YouTube channel's statistics, its uploaded videos, a video's details and the comments people leave, signed in with the channel owner's Google account.
FAQ
Customer.io and MyDeepAgents
Can MyDeepAgents connect to Customer.io?
Yes. The Customer.io connector has 5 actions: 3 read and 2 make changes. Your agents can call them as tools, and your workflows can run them as steps.
How do I connect Customer.io?
Paste an API key from your Customer.io account. You'll need: App API key. The connection also asks for: Region. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.
Can an agent change data in Customer.io without asking?
Only if you let it. Each of the 2 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.
Can I use Customer.io in workflows as well as agents?
Yes. Every Customer.io action also works as a step in a workflow, and the same connection serves your agents and your workflows.
Early access
Put Customer.io to work
Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.