Dynamics 365 Integration
Live

Enterprise CRM
on a live graph.

Native Dynamics 365 connector with integration-dynamics365 graph module — opportunities, contacts, leads, and accounts traverse live via Dataverse Web API alongside Microsoft Graph, Slack, and docs.

Start free trial All integrations
Federation path

Dynamics 365 joins
your full stack.

Dynamics 365
Gyri graph
CRM · comms · docs
What connects

Dynamics 365 data
in your graph.

Data

Opportunities

Data

Contacts

Data

Leads

Data

Accounts

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

The problem

Dynamics 365 alone
is not enough.

01

Dataverse siloed from comms

Pipeline stages live in Dynamics — but pricing threads and support escalations happen in Outlook and Teams.

02

Power Platform vs GTM stack

Sales workflows in Dynamics rarely join product usage signals or engineering blockers in one cited brief.

03

Static CRM exports

Power BI snapshots of Dynamics go stale before reps can answer "what changed on this account since last week?"

With Gyri

Federated, cited,
agent-ready.

Live graph module

Opportunities as graph entities

integration-dynamics365 installs dynamics365_*_live remote types — agents query live Dataverse Web API data.

Cross-source joins

Opportunity → email → Slack

Multihop queries link Dynamics opportunities to Microsoft Graph threads, tickets, and docs in one cited answer.

Microsoft stack

CRM joins M365 context

Federate Dynamics records with Microsoft Graph mail, SharePoint docs, and institutional memory insights.

MCP agents

Agents traverse live CRM

Claude and Cursor read Dynamics 365 through the same graph as humans — research persists across sessions.

Gyri think verbs

26 MCP think verbs —
not API wrappers.

Dynamics 365 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.

Account brief

Join Dynamics opportunity stage with recent Outlook threads and Teams channel history — cited pre-call summary.

Pipeline risk scan

Correlate stalled opportunities with support ticket themes and product feedback from Notion.

Lead handoff

Automated cited synthesis when Dynamics lead status changes — routed to sales with full federated context.

Works with

Federate alongside
native connectors.

HubSpot
Slack
Notion
Pipedrive
Setup

Connect in
minutes.

Azure AD OAuth access token and org URL 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 Dynamics 365 Setup guide

Connect Dynamics 365 to Gyri.

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

Start free trial Browse integrations