Front Integration
Live

Shared inbox intelligence
on a live graph.

Native Front connector with integration-front graph module — inboxes, conversations, and contacts traverse live via REST alongside Slack, CRM, and docs for cited customer comms context.

Federation path

Front joins
your full stack.

Front
Gyri graph
CRM · comms · docs
What connects

Front data
in your graph.

Data

Inboxes

Data

Conversations

Data

Contacts

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

The problem

Front alone
is not enough.

01

Inbox silos

Front holds customer threads — but account context lives across CRM, Slack, and support tools elsewhere.

02

Manual thread briefs

Teams prep replies by copying Front conversations instead of joining federated context in one cited summary.

03

No agent-ready inbox context

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

With Gyri

Federated, cited,
agent-ready.

Live graph module

Inboxes as graph entities

integration-front installs front_*_live remote types — agents query live Front REST data.

Cross-source joins

Conversation → CRM → Slack

Multihop queries link Front threads to HubSpot deals, Zendesk tickets, and Slack mentions.

Routing + GTM stack

Inbox joins revenue tools

Federate Front with CRM pipeline, Gong calls, and institutional memory.

MCP agents

Agents read your inbox

Claude and Cursor access Front through the same cited graph as support and success teams.

Gyri think verbs

26 MCP think verbs —
not API wrappers.

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

Escalation brief

Join Front conversations with HubSpot account history and recent Slack threads — cited handoff summary.

VIP reply prep

Correlate Front contacts with CRM renewals and support ticket themes.

Routing audit

Automated cited synthesis linking Front inbox volume to product feedback in Notion.

Works with

Federate alongside
native connectors.

Setup

Connect in
minutes.

API token from Front Settings → Developers 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 Front Setup guide

Connect Front to Gyri.

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