Claude Customer.io connectorWhat Claude can do in your Customer.io account.
The Claude Customer.io connector exposes 8 tools. 4 read your workspace and its guidance, 2 write or delete through the Customer.io API, and 2 appear on the sheet with no description at all. Below: what Claude can build, what it can remove, and who holds the keys.
Verified Trustpilot reviews · AI, automation & growth agency
What the Claude Customer.io connector changes for lifecycle teams
A lifecycle marketer notices the welcome series converts less than last month. Normally she would export metrics, open each email and compare by hand. With the connector she asks Claude why, and Claude pulls the delivery, open and click data from her Customer.io workspace, reads the automation and points at the step where people drop off.
Diagnose before you touch anything. cio_read_api gives Claude read access to the Journeys and Data Pipelines interfaces: campaign results, customer profiles, deliverability signals. Customer.io's own example is a question like why deliveries dropped this week.
Build from a sentence. Describe an audience, say users inactive for 90 days, and Claude can turn it into a segment through cio_write_api, which also covers automations, broadcasts, newsletters, profile attributes and emails drafted in Design Studio. Before running a write, the connector can show a dry-run preview of what would happen.
Get the setup right the first time. cio_schema lets Claude inspect the structure it is about to use, and cio_skills_list with cio_skills_read give it guidance maintained by Customer.io for tricky jobs such as wiring an automation or writing segment conditions, matched to what your account allows.
What the connector will not do for you: pick the workspace. You grant workspaces and permission scopes when you connect, and in each conversation you tell Claude which workspace to work in. Deletions go through a separate tool, cio_delete_api, and read, write and delete are granted independently. Nothing fires on its own either: no tool wakes up when a customer signs up. That is the job of Customer.io's own automations, or of the tools listed on our Integrations hub.
Five words before you plug it in
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in that account while it answers you.
- Tool
- A named action the connector makes available to Claude. Claude chooses the ones it needs by itself; the directory shows each by name.
- Authorization
- Customer.io's own consent screen, where you pick the workspaces and permissions Claude will use. Given once per person, revocable later.
- Approval
- The confirmation Claude waits for in the conversation before going ahead with something that would alter your workspace.
- MCP
- The common standard behind connectors: the layer that lets an assistant like Claude talk to an outside service such as Customer.io.
Plug Customer.io into Claude in three steps
- 01
Find Customer.io in Claude
In Claude's settings, open Customize then Connectors and look for Customer.io. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector before each member can sign in with their own account.
- 02
Start the connection
Click Connect on its row and sign in to Customer.io in the window it opens. If the link stops working one day, choose Disconnect and connect again from the same list.
- 03
Review the authorization screen
Read Customer.io's authorization screen before you accept: it belongs to the service, not to Claude, and it decides what the access covers. You can revoke that access later from the Customer.io side too.
The 8 tools, sorted by what they do
Customer.io gives Claude 8 tools: 4 that read your account, 2 that change something in it, and 2 no official source describes.
Three groups: what Claude reads, what it writes or deletes, and two tools nothing documents. Names stay as Claude displays them.
- 4 read
- 2 write
- 2 not documented
What Claude reads (4)
4 toolsFour tools that look at your workspace or at Customer.io's guidance without altering anything.
cio_schema
Lets Claude look at the structure behind the Customer.io interfaces before it uses them, so that its requests match exactly what your workspace expects.
cio_skills_list
Shows Claude the guides Customer.io maintains on its side for complex jobs, such as automation wiring, segment conditions or email design patterns.
cio_skills_read
Opens one of those guides so Claude follows Customer.io's current instructions rather than its own memory, scoped to what your own account's offer allows.
cio_read_api
Covers every GET request on the Journeys and Data Pipelines interfaces: campaign results, customer profiles, deliveries, opens, clicks, conversions and pipeline settings.
What Claude writes or deletes (2)
2 toolsTwo tools that act on your workspace. No source describes a confirmation specific to them: the general rule below applies.
cio_write_api
Approval: see the ruleCarries the POST, PUT and PATCH requests: building or editing automations, broadcasts and newsletters, creating segments, updating profiles and publishing Design Studio emails.
cio_delete_api
Approval: see the ruleHandles DELETE requests on your workspace, kept apart from writing so it can be granted or refused on its own.
Not documented (2)
2 toolsThe directory publishes these two names and nothing else. No official text says what they do, and we will not guess from a name.
cio_prime
This name sits in the directory's tool list, and that is all anyone publishes about it. Neither Customer.io's setup page nor the connector description explains it, so this page adds nothing.
cio_auth_status
Listed by name on the directory sheet, with no sentence from any official source describing its role. We leave it at that rather than read meaning into the name.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. The request appears in the conversation when it matters.
On a Team or Enterprise workspace, owners decide whether members may let some actions through without a prompt each time. They can also restrict a connector across the organization, keeping reads open and closing writes, and nobody overrides that from a personal account. Customer.io adds its own layer: read, write and delete are separate permissions you pick per workspace at connect time, and credentials never pass through Claude. Claude inherits your Customer.io rights and nothing more. Active sessions can be reviewed and revoked from Customer.io's personal settings.
Which plans include it
None of the 819 sheets in the official directory states availability by plan. That connector-by-connector answer is not published anywhere, which is a real gap in the catalogue.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before members can sign in. Customer.io's own setup page says something more restrictive, set side by side in the limits section below. For the current state, check the connector's sheet in the official directory.
Where the Claude Customer.io connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing starts when a customer signs up, opens an email or leaves a segment.
Only Customer.io documents this connector: no Claude help article covers it, so these limits come from the publisher's setup page and the directory sheet. The tool list is an observed floor, not a promise, since administrators can open actions no public sheet shows. The partner badge is not a security audit, and Anthropic states on every sheet that it neither chooses the tools a publisher exposes nor guarantees them. For a connector where official sources disagree on sending, compare with the Claude gmail connector.
On which Claude plans can this connector be used?
- Claude Help Center, general connector rule ↗September 2026Remote connectors are open to all users; on Team and Enterprise, an Owner must switch each one on first.
- Customer.io setup page for Claude ↗September 1, 2026The publisher states that MCP support is not available on Claude's free plan and that a paid Claude plan is needed.
What this page followsNeither is outdated: Anthropic's rule covers every connector, Customer.io's line targets this one, but it is the publisher speaking, not Anthropic. Neither settles it for your account: check the connector's sheet in the directory while signed in.
Need help connecting Customer.io to Claude?
A person reads every message.
