Notion integration · MCP and OAuth
Connect AI agents to your Notion workspace
AI agents that read your Notion pages, draft new ones, and post the result to Slack — research briefs, compliance memos, onboarding playbooks, technical docs.
The connection
What's wired
Fidelic agents connect to Notion through the Model Context Protocol (MCP), which exposes your Notion workspace to the agent the way a colleague would have access — through OAuth, with scopes you control. The integration falls back to Notion's REST API directly when an action isn't yet covered by the MCP surface.
The connection lives inside your sandboxed Anthropic project — one project key per Fidelic customer. Notion sees an OAuth app for your workspace; Fidelic infrastructure is not in the path between the agent and your pages.
Two access modes are available. Read-only — the agent indexes pages and databases for retrieval; used by knowledge agents like ZADO-01 to ground Slack answers. Read-write — the agent can create and edit pages in databases the workspace owner explicitly shares; used by writing agents like , OREN-01, and VELA-01 to draft research, docs, and memos in the workspace your team already reads.
Set it up
How to connect
Before you start
- A Notion workspace on any plan — Free, Plus, Business, or Enterprise.
- Workspace owner role, or an admin who can install third-party integrations.
- A Slack workspace where the agent will live and post (the agent shows up in Slack first; Notion second).
- A decision on which databases the agent should reach — knowledge bases for read-only agents, draft destinations for writing agents.
- About five minutes for the OAuth flow plus a thirty-minute background index build.
The steps
- Sign in to Fidelic and pick the agent you want to hire. From the Roster, choose the agent that needs Notion access — ZADO-01 for Slack-grounded knowledge answers, for technical docs, OREN-01 for daily research briefs, VELA-01 for compliance memos. Each agent has a Notion connect button on its setup screen.
- Authorize Notion. Click Connect Notion. The OAuth dialog opens; sign in with your workspace owner account. The app appears in Notion's Settings & Members → Connections panel under the name Fidelic — [agent codename].
- Pick the databases the agent should reach. Notion shows a permissions screen with every database in your workspace. For read-only agents (knowledge agents), select your published-docs databases. For writing agents, select the destination databases the agent will draft into. You can change this any time from Notion's Connections panel.
- Confirm and finish. The agent runs a test read against the first database you shared. When the test passes, your Slack channel shows a Connected to Notion message naming the agent. The full database index builds in the background over the next thirty minutes.
- Try the first agent action. Ask the agent a question in Slack — it will surface the answer with the Notion source link. For writing agents, wait for the next scheduled trigger or a real event and check the destination database for the draft. If nothing fires within an hour, post @[agent] status in Slack and the agent will report what it's waiting on.
The roster
Agents that connect to Notion
ZADO-01
AI Knowledge Curator
Cited Slack answers
OREN-01
AI Research Analyst
Weekly market memo
VELA-01
AI Compliance Analyst
Compliance memos ready for your GC
ELRA-01
AI Onboarding Coordinator
Onboarding flows that don't slip
DRYN-01
AI Data Analyst
Recurring analyses, dashboard maintenance, anomaly watch
DARO-01
AI Technical Writer
Docs that ship with the release
In practice
What they do with it
Searches the indexed Notion pages and databases for the canonical answer
Posts a cited reply in the Slack thread with the source page link
Drafts the morning research brief in the Notion 'Daily Briefs' database
Posts the link in your research channel before the team arrives
Drafts a compliance memo in Notion citing the original source
Tags General Counsel; the memo only ships after legal review
Creates an onboarding playbook page in Notion from your template
Assigns the first three days to the customer-success owner with deadlines
Updates the recurring analysis page in Notion with the week's numbers and a one-paragraph commentary
Marks the previous version archived; pings the analytics channel
Adds the question to the Notion 'Open questions' database
Flags the team in Slack to triage and write the missing doc
The edges
Connection limits
The agent only reaches the pages and databases the OAuth scope explicitly permits. Workspace owners control that scope — adding a database is a one-step Notion permissions change, not a contract negotiation.
Fidelic agents do not currently:
- Modify Notion's database schema. Column types, page templates, and database structure stay under your workspace admin's control.
- Bulk-export entire workspaces. The read pattern is page-by-page and database-by-database, not workspace-wide crawl.
- Author word-anchored comment replies threaded to a specific phrase. We read comment threads; we don't yet position replies on a selection.
- Replace Notion AI's in-page generation. Notion AI is good at the single-page task you initiate from inside Notion. Fidelic agents do work that spans Notion plus your other tools — drafting from a Slack thread, watching an external trigger, posting the result back in chat.
The path
Where the data goes
The Notion connection runs inside your sandboxed Anthropic project. The OAuth credential is stored on Anthropic's infrastructure under your project key, not on Fidelic systems.
When the agent reads a Notion page, the page content passes from Notion through your Anthropic project to the model, and the model's output goes back to Notion or to Slack — never to a Fidelic-operated database. Fidelic operates the agent template; we don't run an intermediate store that holds your Notion content.
Where to next
- → See the Roster — agents you can hire that use this connection
- → See all integrations
- → Notion API docs