Connect Claude to your Customer.io workspace with full read, write, and delete access — granted independently, per workspace, via OAuth.
What Claude can do today: • Build and edit automations (campaigns), broadcasts, and newsletters • Create segments from plain-English audience definitions • Inspect and update customer profiles and attributes • Draft, QA, and publish emails in Design Studio • Analyze deliveries, opens, clicks, and conversions; diagnose deliverability • Manage CDP Data Pipelines: sources, destinations, and reverse ETL • Guide SDK setup and app integration end to end
The connector exposes Customer.io's Journeys UI API and Data Pipelines API through verb-scoped tools — cio_read_api (GET), cio_write_api (POST/PUT/PATCH), and cio_delete_api (DELETE) — so reads, writes, and deletes are approved separately. Built-in schema introspection (cio_schema) and server-maintained skills (cio_skills_list / cio_skills_read) give Claude authoritative, always-current guidance for complex workflows like automation wiring, segment conditions, and email design patterns, scoped to your account's plan.
Safety is built in: every write and delete supports a dry-run preview before execution, and credentials never pass through Claude — authentication is OAuth, with workspaces and permission scopes selected at connect time.
Try: "Analyze last month's welcome automation performance." "Build a segment of users inactive for 90 days." "Draft a re-engagement email and QA it." "Why did deliveries drop this week?"
cio_auth_statusShow the active authentication state. Reports the authenticated user and account, the workspaces the current OAuth token is allowed to access, and whether an agent service-account JWT can be minted. Use this to diagnose auth errors.
cio_delete_apiDelete a resource via the Customer.io API (DELETE only). Always run with dry_run first to preview. Use cio_schema to find the correct path.
pathstringAPI path including placeholders, e.g. '/v1/environments/{environment_id}/campaigns/{campaign_id}'. Placeholders are substituted from params.
dry_runbooleanValidate and return the request without executing it.
jqstringgojq expression to filter the response before returning.
paramsobjectParameters as a nested JSON object (pass the object directly; do not JSON-encode it as a string). Keys matching path placeholders are substituted; remaining keys become the query string.
cio_primePrint LLM-ready instructions for using the Customer.io API. ALWAYS call this first in a new task — it contains the authoritative, version-specific rules for how to drive the API via the other cio_* tools.
cio_read_apiRead from the Customer.io API (GET only). Use cio_schema first to find the correct path and placeholders. Workspace routing is enforced server-side via the caller's OAuth token.
pathstringAPI path including placeholders, e.g. '/v1/environments/{environment_id}/campaigns'. Placeholders are substituted from params.
dry_runbooleanValidate and return the request without executing it.
jqstringgojq expression to filter the response before returning. Use to trim large responses.
limitnumberPage size.
pagenumberPage number (1-indexed).
page_allbooleanAuto-paginate and return NDJSON for the full dataset.
paramsobjectParameters as a nested JSON object (pass the object directly; do not JSON-encode it as a string). Keys matching path placeholders are substituted; remaining keys become the query string.
cio_schemaIntrospect the Customer.io API schema. Use this to discover endpoints before calling cio_read_api / cio_write_api / cio_delete_api — never guess paths or field names. Pass no query to list resources; pass a resource name ('campaigns') to list its endpoints; pass 'resource.method' ('campaigns.list'), 'METHOD /path', or '/path' for endpoint detail.
querystringOne of: '' (list resources), 'campaigns' (resource), 'campaigns.list' (resource.method), 'GET /v1/...' (method + path), or '/v1/...' (all methods for a path).
refreshbooleanForce re-download of API specs.
cio_skills_listList available agent skills — task-specific instruction manuals maintained by Customer.io (routing rules, required params, multi-step workflows).
refreshbooleanForce re-download of skills.
cio_skills_readRead the full content of a specific agent skill. Paths look like 'campaigns' for the main skill or 'campaigns/examples.md' for a sub-file — see cio_skills_list for available paths.
pathstringSkill path, e.g. 'campaigns' or 'campaigns/examples'. See cio_skills_list for available paths.
cio_write_apiWrite to the Customer.io API (POST, PUT, or PATCH). Always run with dry_run first to preview. Use cio_schema to find the correct path, method, and body shape.
pathstringAPI path including placeholders, e.g. '/v1/environments/{environment_id}/campaigns'. Placeholders are substituted from params.
bodyobjectJSON request body as a nested object (pass the object directly; do not JSON-encode it as a string).
dry_runbooleanValidate and return the request without executing it.
jqstringgojq expression to filter the response before returning.
methodstringHTTP method: POST, PUT, or PATCH. Defaults to POST.
paramsobjectParameters as a nested JSON object (pass the object directly; do not JSON-encode it as a string). Keys matching path placeholders are substituted; remaining keys become the query string.