Customer.io
Identify, track, segment and merge people via Customer.io's Track API.
About
Customer.io ships in the w6w first-party pack. It declares 7 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.customerio- Version
- 0.1.3
- Author
- w6w
- Licence
- MIT
- Categories
- Marketing · Email
Overview
Customer.io’s Track API is the write side of customer data — creating and updating people, recording events, managing segment membership, and merging duplicate profiles. This app implements exactly that surface: identify a person (an upsert keyed by id), delete one outright, track a named event either against a known person or anonymously, add or remove people from a segment in batches of up to 1,000, and merge a duplicate profile into its primary.
Customer.io splits its API in two — a write-only Track API for data and a separate App API for campaigns and workspace management — and this app deliberately calls only the Track API, so it has nothing to say about broadcasts, newsletters or campaign configuration. It also respects the platform’s two independent data regions, US and EU, each on its own host with no cross-region fallback, set once at connection time rather than per action.
A few operations carry consequences worth knowing: deleting a person is permanent rather than a suppression, merging a duplicate profile is irreversible since the secondary profile stops existing afterward, and tracked events have no dedupe key, so retrying a failed track call creates a second, distinct event rather than converging on the first.
Build with Customer.io
Three routes to the same 7 actions. The Workflow tab is generated from Customer.io's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Delete Person
delete Permanently delete a person. Does not suppress them — they can be re-added later.
Identify Person
identify Create a person, or update their attributes if they already exist (upsert).
Merge Person Profiles
merge Merge a secondary (duplicate) person into a primary person. The secondary is permanently deleted.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Customer.io's real ids.
{
"manifestVersion": "2",
"name": "customerio-example",
"steps": [
{
"id": "add-to-segment",
"uses": {
"app": "io.w6w.customerio",
"action": "add-to-segment",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"segmentId": "<segmentId>",
"personIds": "<personIds>"
}
}
]
}Here are some of the things you can do
-
Add Person to Segment
performadd-to-segment -
Identify Person
performidentify -
Merge Person Profiles
performmerge -
Track Event
performtrack -
Track Anonymous Event
performtrack-anonymous
+2 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Customer.io, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Customer.io. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "track",
payload: {
personId: "<value>",
eventName: "<value>",
// data: "<value>",
// eventType: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action track --payload '{"personId":"<value>","eventName":"<value>"}'Give an AI agent Customer.io — without giving it Customer.io's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.customerio#add-to-segment",
"input": {
"segmentId": "<segmentId>",
"personIds": "<personIds>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Customer.io connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Customer.io's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Customer.io itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Customer.io declares its own checks, so its health is a property of the app rather than something the host guesses at.
Customer.io platform status
Atlassian Statuspage rollup for status.customerio.com, with per-component detail. Unauthenticated and unsigned.