Checks a person's delivered messages, records events and traits mid-conversation, merges duplicate profiles, and honours unsubscribe requests on the spot.
23actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro manually triggers a Customer.io broadcast campaign to send messages to a defined audience. Support teams can launch targeted communications immediately without waiting for scheduled sends.
Ayro sends an event associated with a person to Customer.io for tracking and analytics. Support agents can record customer actions, creating the data trail that powers personalized follow-ups.
Ayro identifies a person in Customer.io and assigns behavioral traits and attributes to their profile. Agents can enrich customer records with new information, ensuring future communications are targeted correctly.
Each card is one request a support team gets, and the Customerio actions Ayro runs to close it.
Ayro pulls delivery metrics for messages between two timestamps and reads which segments the person belongs to, so a customer asking why they did or did not get a message gets a factual answer.
Ayro identifies the person and writes the traits they gave, tracks the action they took as an event that segmentation can key off, and attaches them to the company or account they belong to.
Ayro unsubscribes a person against the specific delivery they complained about, suppresses the profile when the request is a full deletion, and merges a second identifier into the profile you keep.
Ayro fires an API-triggered broadcast at a named recipient or filter, then reads the trigger record back to confirm the campaign ID, recipient criteria, and processing status.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Customerio actions it has and picks the ones a request needs.
Authorize the Customerio account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Customerio actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeCustomerio · Ayro
What can you do in Customerio without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Customerio.
It can. Customer.io splits its APIs and the toolkit follows that split: Suppress Customer Profile and Unsubscribe from Delivery need Track API credentials, Track Page View needs CDP API credentials, and the segment, message, and newsletter lookups run on the App API. Connect the credential set that covers the actions you want Ayro to take.
All 23 actions your agent can call on Customerio, straight from the live MCP connection.
Add people to a group in Customer.io.
Create an alias to merge multiple profiles in Customer.io.
Suppress a customer profile to permanently delete it and prevent re-adding with the same identifier.
Retrieve a list of integrations in your workspace.
Retrieve a list of messages sent from your workspace.
Retrieve details of a specific segment.
Retrieve people in a specific segment.
Retrieve a list of segments in your workspace.
Retrieves details about a specific API-triggered broadcast, including trigger ID, campaign ID, creation timestamp, recipient filter criteria, and personalization data.
Retrieve all API trigger instances for a specific broadcast/campaign.
Retrieves all reporting webhook configurations from the Customer.io workspace.
Identify a person and assign traits to them in Customer.io.
List all Collections metadata.
Retrieve the list of IP addresses used by Customer.io for sending messages.
List all newsletters.
List all snippets in your workspace.
Lists all transactional message templates in your Customer.io workspace.
Send multiple CDP calls (identify, track, page, screen, group, alias) in a single batch request.
Send an event associated with a person in Customer.io.
Track page view events for website visitors in Customer.io.
Track mobile screen views in Customer.io for analytics and user journey tracking.
Manually trigger a Customer.io broadcast/campaign to send messages to a defined audience.
Handle custom unsubscribe requests for email deliveries in Customer.io.
Same connection, same setup. Pick the next one your team already uses.
Adds and tags subscribers, builds campaigns and resends to non-openers, reports open and click performance, and processes unsubscribe requests.
Answers attendee and availability questions from the live event, creates and publishes events, issues discounts and access codes, and registers webhooks.
Subscribes, tags, and unsubscribes contacts on request, reports campaign opens and clicks, and builds the next send from a saved template.
Searches and verifies wallet passes, records scan events, and pushes bulk updates or notifications to as many as 500 pass holders.
Creates dynamic video campaigns, loads prospects into them in bulk, confirms a prospect's video, and audits campaign webhooks.
Reports pop-up display and conversion metrics, pulls collected contacts, and manages the webhooks that forward new form submissions.

Authorize the account and your agent has all 23 actions from the first conversation.
