Customer.io MCP integration for AI agents.
Connect AI agents to Customer.io through 7 structured actions, including merge customers, delete customer, and identify customer. Review authentication, inpu…
- ACTION CONTRACTS
- 7
- AUTHENTICATION
- Custom credentials
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Customer.io integration exposes
The Customer.io Agent App exposes 7 provider-backed actions for marketing, communication, and data work. Its current contract lets an authorized agent merge two customer.io people, keeping the primary profile and deleting the secondary profile, delete a customer.io person and their information through the track api, and add or update a customer.io person through the track api. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses Custom credentials. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Customer.io account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Customer.io capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
merge_customersWRITEMerge two Customer.io people, keeping the primary profile and deleting the secondary profile.
INPUTS: primary / secondary
delete_customerHIGH IMPACTDelete a Customer.io person and their information through the Track API.
INPUTS: identifier
identify_customerREVIEWAdd or update a Customer.io person through the Track API.
INPUTS: identifier / attributes
suppress_customerREVIEWDelete and suppress a Customer.io person identifier so it cannot be re-added until unsuppressed.
INPUTS: identifier
track_anonymous_eventREVIEWTrack an event for an anonymous person in Customer.io.
INPUTS: anonymousId / name / type / eventId / timestamp
track_customer_eventREVIEWTrack an event associated with an identified Customer.io person.
INPUTS: identifier / anonymousId / name / type / eventId
unsuppress_customerREVIEWUnsuppress a Customer.io person identifier so a new profile can be created later.
INPUTS: identifier
INPUT CONTRACTS
Know what the action needs before it runs.
merge_customers
primaryREQUIRED- A Customer.io person reference identified by exactly one of id, email, or cio_id.
secondaryREQUIRED- A Customer.io person reference identified by exactly one of id, email, or cio_id.
delete_customer
identifierREQUIRED- The Customer.io person identifier in the path. Use the person's id, email address, or cio_id value with the cio_ prefix.
identify_customer
identifierREQUIRED- The Customer.io person identifier in the path. Use the person's id, email address, or cio_id value with the cio_ prefix.
attributesREQUIRED- The Customer.io profile attributes to assign to the person.
suppress_customer
identifierREQUIRED- The Customer.io person identifier in the path. Use the person's id, email address, or cio_id value with the cio_ prefix.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Merge Customers
Merge two Customer.io people, keeping the primary profile and deleting the secondary profile. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
merge_customersControl Merge Customers
Merge two Customer.io people, keeping the primary profile and deleting the secondary profile. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
merge_customersVerify with Delete Customer
Delete a Customer.io person and their information through the Track API. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
delete_customerSAFETY BOUNDARY
Operate Customer.io with explicit limits
- Authorize Customer.io with Custom credentials and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_customer` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Customer.io rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Customer.io task completed successfully.
CONNECTION MODEL
Custom credentials
Customer.io uses Custom credentials. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 0
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 5
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Customer.io.