Customer.io Integration
Live

Behavioral messaging intelligence
on a live graph.

Native Customer.io connector with integration-customerio graph module — campaigns, segments, and broadcasts traverse live via App API alongside Braze, HubSpot, and Slack for cited lifecycle context.

Federation path

Customer.io joins
your full stack.

Customer.io
Gyri graph
CRM · comms · docs
What connects

Customer.io data
in your graph.

Data

Campaigns

Data

Segments

Data

Broadcasts

Auto-provisions graph module: integration-customerio — live API types install when you connect credentials.

The problem

Customer.io alone
is not enough.

01

Messaging silos

Customer.io orchestrates behavioral journeys — but product and CRM context lives across Mixpanel, HubSpot, and Slack elsewhere.

02

Manual journey briefs

Growth teams prep campaign reviews by copying Customer.io exports instead of joining federated CRM context in one cited summary.

03

No agent-ready messaging context

Customer.io dashboards cannot multihop to deal stage, support themes, and cited exec briefs in one query.

With Gyri

Federated, cited,
agent-ready.

Live graph module

Campaigns as graph entities

integration-customerio installs customerio_*_live remote types — agents query live Customer.io App API data.

Cross-source joins

Segment → CRM → product

Multihop queries link Customer.io segments to HubSpot lifecycle stage, Mixpanel events, and Slack GTM threads.

Lifecycle stack

Customer.io joins GTM tools

Federate Customer.io with Braze, Klaviyo, and institutional memory.

MCP agents

Agents read your journeys

Claude and Cursor access Customer.io through the same cited graph as product and revenue teams.

Gyri think verbs

26 MCP think verbs —
not API wrappers.

Customer.io federates into one graph. Agents orient with recall and ground, capture with reflect, and commit with promote — the full epistemic lifecycle via MCP think.

think verb=recall

Semantic orient — load prior cited conclusions before you re-derive from scratch.

think verb=ground

FTS-only orient on live federated CRM, email, and Slack — zero embed cost.

think verb=consider

Classify novelty against the workspace corpus before you commit a thesis.

think verb=reflect

Capture drafts, tensions, and questions as typed thoughts on the graph.

think verb=traverse

Multihop GraphQL in one think call — deal → contact → email → ticket.

think verb=fetch

Hydrate full rows by ref when search or traverse surfaced the right node.

think verb=promote

Gated commit — draft thought → durable cited insight the whole team recalls.

think verb=wish

Natural-language buildout — queue workspace types, connectors, and workflows.

Full catalog via MCP think verb=catalog · Why Gyri think verbs beat API wrappers → · MCP for Claude & Cursor

Use cases

Built for
GTM operators.

Behavioral brief

Join active Customer.io campaigns with HubSpot deal stage and recent product events — cited lifecycle summary.

Segment context

Correlate Customer.io segments with support ticket themes and churn risk signals.

Broadcast review

Link Customer.io broadcasts to LinkedIn Ads spend and landing-page tests in one federated query.

Works with

Federate alongside
native connectors.

Setup

Connect in
minutes.

Customer.io App API key and optional EU host in Settings → Integrations.

1. Start a free trial at app.gyri.io · 2. Open Settings → Integrations · 3. Run your first federated query with cited answers.

Connect Customer.io Setup guide

Connect Customer.io to Gyri.

Free trial — API credentials, auto graph module, cited federated answers.