Integrations · ProductivityConnect Granola to Well
Index Granola meeting note, transcript, and attendee so questions about audit entry and indexed record answer themselves in conversation.
What Well pulls from Granola
Granola feeds meeting note, transcript, attendee into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Granola’s access.
| From Granola | In Well | Relation | |
|---|---|---|---|
| Meeting note | Audit entry | Captures as | |
| Transcript | Indexed record | Becomes | |
| Attendee | Team member | Resolves to |
- Sync mode
- MCP hybrid
- Refresh
- live + reconciliation reads
- Direction
- Granola → Well
What Well does with your Granola connection
Connect
Connect Granola over OAuth (MCP DCR): Well registers a client through Granola's OAuth Dynamic Client Registration and you approve on Granola's side, so the password never reaches Well; Well holds only a scoped token it can refresh.
Sync
Well brings meeting note, transcript, and attendee in from Granola on live events backed by periodic reconciliation reads. The first sync backfills history in the background and the connection stays live after.
Enrich
Well resolves each Granola entity into audit entry, indexed record, and team member, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Available
Your data from Granola lands in the workspace as audit entry, indexed record, and team member you can search, chart, and automate.
Questions Granola unlocks
Ask in plain language. Well answers from your connected Granola connection, resolved against the rest of your stack.
Ask anything about your Granola connection
Ask about your Granola connection…
Connect Granola in three steps
- 01
Authorise Granola via MCP
From Well's Connections panel, search for Granola and click Connect. Well discovers Granola's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Granola's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.granola.ai/mcp
- 02
Map your entities
Well's MCP client discovers meeting note, transcript, and attendee from Granola that Granola's MCP server exposes and brings them into your workspace using the canonical mappings defined in Well's data-views layer. You can inspect the workspace data model from Settings > Data Model.
- Mappingpreconfigured by Well
- 03
Use the data
Ask questions in conversation, build records tables, or let agents act on Granola records. Because Granola ships through MCP, Well treats every entity it exposes as queryable graph state alongside the rest of your connected tools.
- First syncstarts as soon as connect completes
MCP handshake typically completes under a minute on warm connections. Resource enumeration runs immediately after; full backfill of historical Granola records happens in the background.
How Granola stays secure with Well
Well connects to Granola's MCP server (mcp.granola.ai/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Granola secret. Tokens are scoped to the meeting note, transcript, and attendee Granola exposes and refreshed server-side. Reads only, Well cannot modify or delete Granola records.
- granted
Read Granola records
Resources the Granola MCP server exposes, scoped by your OAuth approval.
- granted
Resolve meeting note, transcript, and attendee across your stack
Match identifiers in Granola against the same entities your other connected tools expose, so each record carries cross-tool context.
- refused
Modify or delete Granola records
Not granted; Granola is read-only in Well. Write-back is opt-in per connector when a write surface exists.
- refused
Store Granola passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
Frequently asked questions about Granola and Well
From Well, open Connections, find Granola, and click Connect. Well discovers the OAuth metadata at mcp.granola.ai/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Granola's side. No client_id or client_secret to paste; the handshake takes roughly a minute.
Well brings in meeting note, transcript, and attendee from Granola and reshapes each entity into your workspace: meeting note becomes audit entry; transcript becomes indexed record. Every record arrives with the source identifier preserved, so Granola stays the source of truth while Well lets you query the data alongside the rest of your stack.
Status transitions on Granola items linked to customer or deal entities surface as workspace events. A task slipping past its due date on a top-tier customer's project, a ticket reopening, a milestone marked at risk; each shows up on the relevant customer page so account owners see the signal before the customer raises it.
Each Granola meeting note is scored against the candidate audit entrys in your workspace on identifier overlap, amount or quantity match, date proximity, and counterparty resolution. Matches above the auto-link confidence threshold flow through cleanly; below the threshold they queue for a one-click human review, with the most likely audit entry prefilled and the Granola source attached.
Well combines live Granola events with periodic reconciliation reads of meeting note, transcript, and attendee. New rows appear within seconds when Granola pushes them; periodic reads catch anything a push missed. The first connect backfills history from Granola in the background.
Open Connections > Granola in Well and click Disconnect. Well calls Granola's token revocation endpoint and stops calling Granola immediately on its side; provider-side propagation to Granola's admin panel varies by provider. The meeting note, transcript, and attendee Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.
Granola records are stored in the region Well operates for your workspace. Specific region details and the steps to change region are available from Support. See /privacy for the current data-handling policy.
Pairs well with Granola
More in Productivity
Asana
Connect Asana to Well to sync tasks, projects, and team workflows.
Atlassian
Connect Atlassian to Well to sync tasks, projects, and team workflows.
Circleback
Connect Circleback to Well to sync tasks, projects, and team workflows.
ClickUp
Connect ClickUp to Well to sync tasks, projects, and team workflows.
Popular cross-category
Ready to connect Granola?
Connect once. Every meeting note, transcript, attendee from Granola becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.