Klaviyo Integration
Live

Lifecycle marketing
on a live graph.

Native Klaviyo connector with integration-klaviyo graph module — lists, campaigns, and profiles traverse live via REST alongside CRM, Slack, and docs for cited lifecycle context.

Federation path

Klaviyo joins
your full stack.

Klaviyo
Gyri graph
CRM · comms · docs
What connects

Klaviyo data
in your graph.

Data

Lists

Data

Campaigns

Data

Profiles

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

The problem

Klaviyo alone
is not enough.

01

Lifecycle siloed from GTM

Email and SMS performance lives in Klaviyo — but retention decisions reference CRM pipeline, support themes, and product usage elsewhere.

02

Manual segment briefs

Marketers export Klaviyo lists before campaigns instead of joining federated account context in one cited summary.

03

No agent-ready lifecycle context

Klaviyo UI does not expose multihop joins for Claude or Cursor to answer cross-stack nurture questions with citations.

With Gyri

Federated, cited,
agent-ready.

Live graph module

Profiles as graph entities

integration-klaviyo installs klaviyo_*_live remote types — agents query live Klaviyo REST data.

Cross-source joins

Campaign → CRM → comms

Multihop queries link Klaviyo campaigns to HubSpot contacts, email threads, and support tickets.

Lifecycle + revenue

Email joins GTM stack

Federate Klaviyo sends with pipeline forecasts, product analytics, and institutional memory insights.

MCP agents

Agents read your lifecycle data

Claude and Cursor access Klaviyo through the same cited graph as marketing and growth teams.

Gyri think verbs

26 MCP think verbs —
not API wrappers.

Klaviyo 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.

Win-back brief

Join Klaviyo profile segments with CRM churn reasons and recent support threads — cited re-engagement summary.

Launch coordination

Correlate Klaviyo campaign status with product release notes in Notion and Slack announcements.

VIP nurture

Automated cited synthesis linking Klaviyo flows to Gong call outcomes and deal stage in HubSpot.

Works with

Federate alongside
native connectors.

Setup

Connect in
minutes.

Private API key from Klaviyo Settings 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 Klaviyo Setup guide

Connect Klaviyo to Gyri.

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