Home/Docs/Customer.io
📣Marketing

Customer.io

Identify people, record the events and page views that describe them, and put them into groups — so a workflow can drive a lifecycle campaign from what actually happened in your product.

⚠️
Not yet connectable

Customer.io is mapped and documented, but one-click connection isn't live yet — the app shows it as Coming soon. Only Google Calendar, Drive, Mail, and Tasks are connectable today; see the Standard integrations catalogue for what's live now.

Category📣 Marketing
ConnectionComing soon not yet connectable — once live it will connect via API key.
Actions5 total — 0 read, 5 write
🔌ConnectFind it in the catalogue
🔐AuthorizeOne-click OAuth
Use actionsChat · agents · workflows
How Customer.io fits into Your Office AI

Actions

Once connected, Customer.io exposes the following actions. The AI can call them with #-mentions in chat, an agent can be granted a subset as tools, and a workflow can run them in an integration-action node.

ActionTypeWhat it doesProxy
Merge Person IDs
alias-person
WriteTell Customer.io that two ids are the same person — the usual case being an anonymous visitor who has just signed up. Merging cannot be undone.Yes
Add Person to Group
group-person
WriteAssociate a person with an account, workspace or company, and set that group's attributes.Yes
Identify Person
identify-person
WriteCreate or update a person in Customer.io. Sending the same id again updates the traits rather than adding a second person.Yes
Track Event
track-event
WriteRecord something a person did. Customer.io campaigns trigger off these, so the event name is what a marketer builds against — keep it stable.Yes
Track Page View
track-page-view
WriteRecord that a person viewed a page.Yes
ℹ️
Write actions are confirmation-gated

Actions tagged Write create, update, or delete data. In chat and agent paths they pause for your confirmation before running; workflows treat their deterministic wiring as implicit consent. Agent tools covers how to scope which actions an agent may use.

Spend & quota

Customer.io is governed per organization: an admin sets a monetary spend cap and a monthly call quota. A quota of 0 disables the integration — it never means unlimited. See the Integrations overview for the full governance model.