Notion Connector

Coppermind's Notion connector is a full read-write integration: it ingests your Notion pages into the right client mind, writes memory-aware meeting recaps back into Notion as native blocks, posts pre-meeting prep comments, and privately nudges you when your client knowledge is thin. Every write is append-only, stamped, and opt-in - Coppermind never edits or deletes anything you've written.

There's one Notion connection per workspace. You connect it once, then tell Coppermind which client each page or database belongs to.

Connect#

You can connect from either place - they do the same thing.

From the dashboard: go to hq.coppermind.app → Settings → Connectors, and click "Connect" on the Notion card.

From Claude:

connectors action=connect source_type=notion

Either way, Coppermind gives you a Notion sign-in link. Open it, sign in, and Notion shows you its own page picker - choose exactly which pages and databases to share. Coppermind only ever reads what you select there. Nothing else in the workspace is visible to it, and only pages you shared get pulled in on each sync.

Route your pages to the right client#

After you approve access in Notion, you land back on the Connectors page in the dashboard. This is where you tell Coppermind which client each page belongs to.

Find the Notion row and click "Route pages." You'll see every top-level page and database you shared, each with a dropdown to assign it to a client mind. Pick the client for each one and you're done - that page (and everything under it) now feeds that client's memory.

Anything you don't route isn't lost. Coppermind auto-files unrouted pages to whichever client mind looks like the best match based on content, and falls back to your Company Mind if it can't tell. Nothing is ever dropped. If you'd rather unrouted pages wait for you instead of being auto-filed, there's an optional "hold" setting on the connector that skips them until you route them - most people won't need this, but ask if you want it turned on.

Right after connecting, give it a minute. Notion needs a little time to index new pages, so the routing panel may look empty at first. Hit Refresh and they'll show up.

Sharing more pages later#

If you want Coppermind to see more of your workspace, just re-run Connect from the Connectors page - that re-opens the Notion picker where you can add more pages or databases. Any newly shared top-level page shows up in the routing panel marked "not routed" until you assign it to a client.

If you had the old per-client Notion setup#

Coppermind used to require a separate Notion connection for every client. If you set those up before, they keep working exactly as before - nothing breaks and nothing is turned off automatically.

When you're ready to switch to the new single-connection model:

1. Connect the new Notion workspace connection (above) - you'll see a banner on the routing panel noting your old connections are still active.
2. Route your pages to the right clients.
3. Click "Retire old connections" on the banner.

Your old connections stop polling, but every memory they already ingested stays exactly where it is - nothing gets deleted or re-processed.

What Coppermind Reads#

For each shared page, Coppermind walks the page's content and flattens it to text - headings, paragraphs, lists, to-dos (with checked state), toggles, callouts, quotes, code, and table rows. Nested blocks are followed up to several levels deep. For a shared database, each row is ingested as its own page. Pages in the Notion trash are skipped.

Content syncs roughly every 15 minutes. Editing a page re-ingests the update without duplicating the prior version.

Writing Back to Notion#

Coppermind can write meeting recaps and prep comments back into your client's Notion pages. All writes follow strict safety rails:

• Opt-in only. Nothing is written until you designate trusted pages.
• Append-only. Coppermind only appends new blocks or posts comments. It never edits, moves, or deletes existing content.
• Stamped. Every section and comment carries a visible "Generated by Coppermind" marker.
• Native blocks. Headings, bullets, callouts - never raw markdown dumped as text.
• Deduped. One recap per meeting, one prep comment per meeting. No spam.

Step 1: Designate Trusted Pages#

Before Coppermind can write, you choose which Notion pages it's allowed to write to:

From Claude:

connectors action=set_write_targets mind_id="<client-mind-id>" page_ids=["<notion-page-id>"]

From the dashboard: Open the Connectors tab, find your Notion connection, and use the trusted-pages picker to select which pages Coppermind may write to.

Pass an empty array [] to revoke all write access.

Step 2: Meeting Recaps (automatic or manual)#

When a meeting transcript is ingested (from Granola, Fireflies, Zoom, or O365 Calendar), Coppermind automatically:

1. Generates a structured recap from the memories extracted during the meeting - summary, key decisions, and action items.
2. Searches the client's prior decisions and commitments for contradictions ("this conflicts with the May 15 decision").
3. Appends the recap as native Notion blocks to the first trusted page.
4. Posts any genuine contradictions as non-destructive Notion comments.

You can also trigger a recap manually:

briefing action=write_meeting_recap

Or target a specific page and meeting:

briefing action=write_meeting_recap page_id="<notion-page-id>" meeting_id="<meeting-log-id>"

Step 3: Pre-Meeting Prep Comments#

Before a scheduled client call, Coppermind can post a prep comment to the client's trusted Notion page summarizing:

• Open commitments (with overdue items flagged)
• Recent key decisions

briefing action=post_prep_comment meeting_id="<meeting-log-id>"

Prep comments are rendered directly from memory - no LLM synthesis needed, so they're fast and cheap.

Knowledge-Gap Nudges (Private)#

When your memory on a client is thin, Coppermind nudges you privately - never on a client-visible page. If your personal mind has a Notion connector with trusted pages, the nudge appears as a comment there. Otherwise it's stored as a quick note on your personal mind and surfaces in your morning briefing.

Beta Customer Setup Script#

Use this copy when walking a beta customer through setup:

1. In Coppermind, go to hq.coppermind.app -> Settings -> Connectors and click
   "Connect" on the Notion card. (Or ask Claude: connectors action=connect
   source_type=notion)

2. Open the returned link in your browser. On the Notion screen, click
   "Select pages" and choose the pages or databases you want Coppermind to
   read (e.g. a client's meeting-notes database or a brand/strategy page).
   Then approve.

3. You'll land back on the Connectors page. Click "Route pages" on the
   Notion row and assign each top-level page or database to the right
   client. If the list looks empty, wait a minute and hit Refresh - Notion
   takes a moment to index new shares.

4. Anything you don't get to isn't lost - Coppermind auto-files it to the
   best-matching client, or your Company Mind if it can't tell. You can
   always come back and route it properly later.

5. (Optional) To enable meeting recap write-back, designate trusted pages
   from the same Connectors tab using the trusted-pages picker, or ask
   Claude: connectors action=set_write_targets mind_id="<client-mind-id>"
   page_ids=["<notion-page-id>"]

"I connected it but nothing showed up"#

Almost always this means the pages weren't shared with the connection. On the Notion authorization screen you must explicitly select the pages/databases to share - granting access to the workspace alone is not enough. Re-run Connect and pick the specific pages, then check the routing panel again (hit Refresh - Notion can take a minute to index new shares). Notion's last_edited_time is minute-resolution, so a page edited in the current minute may land on the next sync rather than instantly.

If a page still isn't routed, it hasn't been dropped - it's either sitting in your Company Mind (auto-filed) or, if you've turned on the "hold" setting, waiting in the routing panel for you to assign it.

Disconnect#

connectors action=disconnect connector_id=<id>

This clears the stored Notion credentials, marks the connector inactive, and stops future syncing. Memories already ingested are preserved.