Ashby Integration
Live

Modern ATS
on a live graph.

Ashby recruiting pipeline federated with Greenhouse, Lever, email, Slack, and docs — candidates and interview plans traverse the graph for cited hiring intelligence.

Federation path

Ashby joins
your full stack.

Ashby
Gyri graph
CRM · comms · docs
What connects

Ashby data
in your graph.

Data

Candidates

Data

Jobs

Data

Interview schedules

Data

Pipeline analytics

The problem

Ashby alone
is not enough.

01

ATS siloed from ops

Ashby holds hiring pipeline — but role context and team capacity live in Slack, Notion, and engineering tools without cited joins.

02

Manual interview prep

Recruiters export Ashby profiles before every interview instead of federated company context on the graph.

03

No agent-ready hiring context

Ashby analytics cannot multihop to roadmap blockers, support hiring signals, and institutional insights in one answer.

With Gyri

Federated, cited,
agent-ready.

Modern ATS

Candidates on the graph

Ashby jobs and candidates index alongside Greenhouse and Lever for federated search.

Cross-source joins

Candidate → role → comms

Multihop queries link Ashby pipeline stages to Slack hiring channels and Gmail threads with citations.

Hiring + ops

Pipeline joins capacity

Federate Ashby open roles with engineering headcount docs and cited institutional hiring insights.

MCP agents

Agents read hiring context

Claude and Cursor traverse cited Ashby data on the same graph as recruiting and hiring managers.

Gyri think verbs

26 MCP think verbs —
not API wrappers.

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

Interview brief

Join Ashby candidate profile with role requirements and Slack hiring context — cited prep summary.

Pipeline review

Correlate Ashby stage metrics with Greenhouse benchmarks and cited time-to-fill insights.

Offer prep

Link Ashby offer stage to compensation docs in Notion and cited finance context.

Works with

Federate alongside
native connectors.

Setup

Connect in
minutes.

Ashby API key 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 Ashby Setup guide

Connect Ashby to Gyri.

Free trial — API key, cited federated recruiting context.