Notion
Sync PM notes, research documents, and meeting notes from Notion
Notion
Connect Notion so Atisbo automatically syncs your product notes, research documents, and meeting notes as internal signals.
Prerequisites
- A Notion account with permission to create integrations
- The databases or pages you want to sync must be shared with the integration (explained below)
Setup
Step 1 — Create an integration in Notion
- Go to notion.so/my-integrations
- Click + New integration
- Give it a name (example: "Atisbo")
- Select your workspace
- Click Submit
- Copy the token that appears (it starts with
secret_orntn_) — you'll need it in the next step
Step 2 — Share your databases with the integration
For each database you want to sync with Atisbo:
- Open the database in Notion
- Click Share (top right corner)
- In the invite field, search for and select your "Atisbo" integration
- Click Invite
If you don't share a database with the integration, Atisbo won't be able to access its content. You need to do this step for each database you want to include.
Step 3 — Hand the token to your agent
Notion has no card in Settings. Tell your agent to connect Notion and give it the token when it asks:
You: Connect Notion. Here is the integration token:
ntn_...
The agent creates the connection and confirms it. There is no consent screen for this one — the token you created in step 1 is the grant, which is why it is the one credential you have to hand over yourself.
Treat that token like a password. It grants read access to every database you shared in step 2, and it is stored encrypted once the agent hands it over.
Done
Atisbo imports the content from the databases you shared right away, and then syncs once a day. If you need fresh changes before the next daily run, ask your agent for a sync now.
What Atisbo Captures
| Notion content | Captured |
|---|---|
| Page text | Yes |
| Nested blocks inside a page | Yes |
| Pages with less than 50 characters | No — filtered for lack of content |
| Templates | No — always ignored |
| Deleted or archived pages | Not removed from Atisbo — evidence is permanent |
Automatic Classification by Database Name
Atisbo automatically classifies signals based on your database name:
| If the database name contains... | Classified as... |
|---|---|
| "Product", "Roadmap", "PRD" | Internal PM signal |
| "Engineering", "Tech" | Internal engineering signal |
| "Design", "UX" | Internal design signal |
| "Customer", "Research" | Customer signal |
| Any other name | General internal signal |
You don't need to configure this — Atisbo infers it from the name. There isn't a custom per-database mapping screen in Settings yet, so descriptive database names matter.
Best Practices
- Sync your research and interview databases — these are the richest sources of product signals
- Use descriptive names for your Notion databases: "Customer Research Q1" is automatically classified as a customer signal
- Don't share operational task databases (sprints, technical backlogs) — they generate noise without discovery value
- Meeting notes are gold — if you have a database of meeting notes, share it with Atisbo
- Combine with other sources: research notes in Notion plus support tickets about the same topic is what turns a hunch into an Opportunity with weight behind it
Disconnecting Notion
Ask your agent to pause or disconnect the Notion connection. Previously processed signals are preserved — disconnecting stops new pages arriving, it does not erase evidence you already have.
To cut access off at the source instead, remove the integration in Notion → Settings → Connections. That works whether or not Atisbo knows about it.