How to Use the Claude Notion Connector

The Claude Notion connector gives Claude read access to the Notion pages you authorize, so you can ask Claude to reference your wiki, project notes, or documentation without copying content into every conversation. Once connected, Claude draws on those pages in any session where it is available.

The connector works with Claude.ai's Projects feature, so you can limit a Notion source to one project's conversations. For decisions and progress that live outside Notion, tools like fenbs provide a complementary work record that any connected assistant reads at session start.

Connect Notion to Claude

Open Claude.ai and navigate to Settings. Find the Integrations section and locate Notion in the list. Click Connect. Claude will redirect you to Notion's authorization page, where you sign in and choose which pages, databases, or workspace sections Claude can access.

Choose the pages that are relevant to your work with Claude. You can adjust the selection later from Notion's own Connected Apps settings—Claude does not control which pages you include; that is managed on the Notion side. Once you confirm the authorization, Claude.ai shows Notion as a connected integration.

This step also covers how to share Notion pages with Claude in detail, including what to select and how to verify access. The connector walkthrough here focuses on what happens after authorization.

Use Notion content in a conversation

With the connector active, start a conversation in Claude.ai and ask about something in your Notion pages. You do not need to mention Notion by name; Claude checks its connected sources automatically. Ask "What does our style guide say about headings?" or "Summarize the onboarding checklist." Claude reads the relevant page and uses its content to answer.

You can also ask Claude directly what Notion content it can access. This is a useful check after first connecting, or when you have updated the page selection in Notion and want to confirm Claude sees the changes.

The connector reads content at the time of the request. If a Notion page changes during a session, Claude may reflect the old version until it re-reads the page. For frequently updated content, verify the answer against the live Notion page before acting on it.

Add Notion as a source in a Claude Project

If you want Notion content available in every conversation within one project—without making it available everywhere—use Claude Projects. Open the project, find the option to add sources, and select the Notion pages you want to include for that project specifically.

A project-level Notion source keeps the scope clear: the development project's Claude session can reference the development wiki, and the marketing project references the brand guidelines. Neither bleeds into the other. See Claude connectors explained for a broader picture of how project and account scopes interact.

What the connector cannot do

The standard Claude Notion connector reads pages; it does not create, edit, or delete Notion content. If you need Claude to write to Notion—create a new page, update a database entry—that requires a Notion MCP server configured for write access, which is a developer-level setup beyond the built-in connector.

The connector also does not replace a work record. Notion is good for documentation that changes slowly: wikis, style guides, meeting templates. It is less suited to tracking the current state of a task, recording a decision that was just made, or noting where a session was left. That is the gap a separate work tool fills.

Keeping handoffs clean when using Notion with Claude

When a session ends and a new one begins—whether that is tomorrow, on a different device, or with a different AI app—the Notion pages stay readable through the connector. What is harder to preserve is the progress from the previous session: what was decided, what was completed, what remains.

A clean handoff combines a Notion connector for the reference material with a saved progress record for the work state. The reference material tells Claude the rules and the background; the progress record tells it where to continue. Without both, each new session either re-reads more than it needs to, or starts from an incomplete picture.

How to do this with fenbs

1. Create a free account and set up a project on your fenbs board. Add the tasks and write the standing rules in Decisions and rules.
2. Connect Notion to Claude.ai following the steps above, then add the relevant pages as a source in the Claude Project for this work.
3. Connect Claude to fenbs via MCP from Integrations. At the start of each session, Claude reads the fenbs context—Rules, Where we left off, In progress—alongside the Notion pages.
4. During the session, Claude can add tasks, record decisions, and save progress in fenbs without leaving the conversation. Notion stays as the reference layer; fenbs holds the live state.
5. Before closing a session, ask Claude to save progress on the tasks it touched. The next session, in any connected app, picks up from an accurate record.