Integrations · Productivity

Connect Notion to Well

Name: Notion entities in Well
Creator: Well

Index Notion page, database row, and person so questions about document and record answer themselves in conversation.

What Well pulls from Notion

Notion feeds page, database row, person into Well as a source. The connection is read-only; disconnect at any time from your workspace settings to revoke Notion’s access.

From Notion	In Well	Relation
Page	Document	Indexes as
Database row	Record	Maps to
Person	Team member	Resolves to

Sync mode: MCP hybrid
Refresh: live + reconciliation reads
Direction: Notion → Well

What Well does with your Notion connection

Connect

Connect Notion over OAuth (MCP DCR): Well registers a client through Notion's OAuth Dynamic Client Registration and you approve on Notion's side, so the password never reaches Well; Well holds only a scoped token it can refresh.

Sync

Well brings page, database row, and person in from Notion 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 Notion entity into document, 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 Notion lands in the workspace as document, record, and team member you can search, chart, and automate.

Questions Notion unlocks

Ask in plain language. Well answers from your connected Notion connection, resolved against the rest of your stack.

Ask Well

Ask anything about your Notion connection

Summarise this month

What needs attention?

Find unmatched records

Ask about your Notion connection…

Connect Notion in three steps

01
Authorise Notion via MCP
From Well's Connections panel, search for Notion and click Connect. Well discovers Notion's MCP OAuth metadata from its .well-known endpoint, registers a client via Dynamic Client Registration, and routes you through the authorize prompt on Notion's side. No client credentials to paste.
- AuthOAuth (MCP DCR)
- DiscoveryMCP .well-known
- MCP servermcp.notion.com/mcp
02
Map your entities
Well's MCP client discovers page, database row, and person from Notion that Notion'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 Notion records. Because Notion 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 Notion records happens in the background. Notion developer docs.

How Notion stays secure with Well

Well connects to Notion's MCP server (mcp.notion.com/mcp) via the Model Context Protocol. The MCP server itself handles credential issuance through OAuth Dynamic Client Registration; Well never sees a long-lived Notion secret. Tokens are scoped to the page, database row, and person Notion exposes and refreshed server-side. Reads only, Well cannot modify or delete Notion records.

OAuth (MCP DCR)Encrypted at restGDPR compliant

Read the full privacy and security policy

Scopes Well requestsmcp.notion.com/mcp

Read Notion records
Resources the Notion MCP server exposes, scoped by your OAuth approval.
granted
Resolve page, database row, and person across your stack
Match identifiers in Notion against the same entities your other connected tools expose, so each record carries cross-tool context.
granted
Modify or delete Notion records
Not granted; Notion is read-only in Well. Write-back is opt-in per connector when a write surface exists.
refused
Store Notion passwords or session cookies
Authentication runs through OAuth (MCP DCR) tokens we never see.
refused

Disconnect any time from Well settings or Notion’s admin panel.

Frequently asked questions about Notion and Well

From Well, open Connections, find Notion, and click Connect. Well discovers the OAuth metadata at mcp.notion.com/mcp/.well-known/oauth-authorization-server, registers a client on the fly via Dynamic Client Registration, and walks you through the authorize prompt on Notion's side. No client_id or client_secret to paste; the handshake takes roughly a minute.

Well brings in page, database row, and person from Notion and reshapes each entity into your workspace: page becomes document; database row becomes record. Every record arrives with the source identifier preserved, so Notion stays the source of truth while Well lets you query the data alongside the rest of your stack.

Status transitions on Notion 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.

Every workspace document built from Notion carries the source page identifier plus a deep link back to the original record. From a workspace page, one click takes you to the Notion record; from Notion, the workspace identifier travels back so you can search either direction. The link survives every subsequent enrichment Well runs.

Well combines live Notion events with periodic reconciliation reads of page, database row, and person. New rows appear within seconds when Notion pushes them; periodic reads catch anything a push missed. The first connect backfills history from Notion in the background.

Open Connections > Notion in Well and click Disconnect. Well calls Notion's token revocation endpoint and stops calling Notion immediately on its side; provider-side propagation to Notion's admin panel varies by provider. The page, database row, and person Well already synced stay in your workspace by default; ask Support to purge them if your compliance flow requires it.

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