Customer.io Pipelines API integration for AI agents.
Customer.io Pipelines API integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Customer.io Pipelines API tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
Real Customer.io Pipelines API actions, managed and audited.
Your user connects Customer.io Pipelines API once; your agent can then send people, events, pageviews, screenviews, groups, aliases, and batch data to Customer.io through the Data Pipelines API — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 1
Your user grants Customer.io Pipelines API access once (OAuth) — the token lands in the vault.
- 2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 3
Every routed call appends a hash-chained audit record — nothing leaves your infra.
Supported Customer.io Pipelines API tools.
7 tools are generated from the published Customer.io Pipelines API catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.
Showing 7 tools. All published catalog entries are included in this page's server-rendered HTML.
- Merge profiles
- *You **only** need to use this method to support a few select destinations like Mixpanel.* The `alias` method reconciles identifiers in systems that don't automatically handle identity changes—like when a person graduates from an anonymous user to an identified user. For example, a person typically has an `anonymousId` until you identify them by `userId`. Most destinations will automatically associate data from the anonymous ID with the new user ID when you send an `identify` call. But a select few destinations, like [Mixpanel](/integrations/data-out/connections/mixpanel/), won't! The `alias` call tells Mixpanel to represent the `anonymousId` with the new `userId`. If you need to use the `alias` call, you'll want to send it before you identify someone with a `userId`. If you use our web or server-side libraries, and you've already identified someone, we assume that this is the `userId` that you want to keep. Otherwise, you need to pass both the `previousId` and the `userId`. **When you use our libraries, you'll typically only provide the `previousId` and `userId`. The libraries fill in the rest of the payload automatically.**
- alias
- Batch requests
- The batch method helps you send an array of `identify`, `group`, `track`, `page` and/or `screen` requests in a single call, so you don't have to send multiple requests. Our server-side sources use this method automatically to increase performance. Requests are limited to 500KB total per request and 32KB per call in the request. In a batch request, the `context` and `integrations` objects apply to _all calls in the request_. You can't set different context or integrations values for different calls in the same request.
- batch
- Create objects and relationships
- Group calls add people to a group. Groups could be a companies, accounts, online classes, and so on. How groups are represented in your destination depends on the destination. Some destinations have concepts of "groups"; Customer.io's destination calls groups "objects." **When you use our libraries, you'll typically only provide an ID for the user, the `groupId`, and `traits`. The libraries fill in the rest of the payload automatically.**
- group
- Add and Update People
- Identifies a person and assigns `traits` to them. In most cases, you'll identify people with a `userId` or an `anonymousId`. But when you use Customer.io as a destination, you can pass an empty `userId` or `anonymousId`, and identify people by their `email` trait. **When you use our libraries, you'll typically only provide an ID and `traits`. The libraries fill in the rest of the payload automatically.**
- identify
- Track pageviews
- Sends a page view event. If you use our JavaScript source, it automatically records `page` events whenever it loads (every page). If you use a single-page app, you'll need to call the `page` method people change routes. The request consists of the page `name` and additional properties about the page. If you use our JavaScript library, the page name and URL are automatically gathered and passed as event properties. **When you use our libraries, you'll typically only provide a user ID/anonymous ID and the `name` of the page. The libraries fill in the rest of the payload automatically.**
- page
- Track mobile screenviews
- Sends a screen view event for mobile devices. Screen events help you understand the screens that people use in your app. You should send a screen call whenever a user requests a page of your app.
- screen
- Track events
- Send an event associated with a person. The `track` call is how you record the things that people do on your website or in your app. While this endpoint takes any `event` name you want to send, Customer.io also supports "semantic events." These are specific `event` names (like `User Deleted` or `Device Created or Updated`) that perform special operations in Customer.io like deleting people, adding mobile devices to profiles, and so on. See the [Customer.io Semantic Events documentation](/integrations/api/cdp/customerio/) for complete schemas and examples. **When you use our libraries, you'll typically only provide an `event`, an ID for the person, and `properties`. The libraries fill in the rest of the payload automatically.**
- track
Customer.io Pipelines API integration, answered
- How do AI agents use Customer.io Pipelines API through Open Connector?
- Your user connects Customer.io Pipelines API once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Customer.io Pipelines API tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a Customer.io Pipelines API MCP server?
- Yes. Open Connector can serve Customer.io Pipelines API as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Customer.io Pipelines API actions with credentials injected server-side.
- Where do Customer.io Pipelines API credentials live?
- In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.
Give your agents Customer.io Pipelines API — keep the keys.
Open source, self-hostable, with Customer.io Pipelines API credentials that never leave your infrastructure. Run it from source today.