Overview
Notion connects in one of two modes:- CRM mode — Thread watches a Notion database and creates accounts when a row’s status property hits the values you pick. An alternative to HubSpot/Salesforce for teams that run ops in Notion.
- Knowledge base mode — Thread reads your Notion pages and databases as context for agents, without acting as a CRM.
Thread connects one CRM at a time. Notion in CRM mode counts against that; Notion as a
knowledge base doesn’t, so it can sit alongside HubSpot or Salesforce. If another CRM is
already connected, Notion connects straight into knowledge base mode.
Benefits
Ops-Friendly
Ops team works in familiar Notion interface
Auto-Trigger CS
New database row → Account created automatically
Flexible Structure
AI extraction adapts to your database structure — no field mapping to author
Knowledge for Agents
Pages and databases readable by agents in knowledge base mode
Setup Instructions (CRM mode)
1
Connect Notion OAuth
Connectors → Notion → “Connect” → Select workspace → Grant access to the pages and
databases Thread should see → Authorize
2
Select the Database
The setup flow lists the databases you shared — pick the one that holds your customer records.
3
Pick the Status Property and Trigger Values
Choose the database’s status property and which of its values should trigger account creation
(e.g. “Closed Won”, “Ready for Onboarding”). You can pick more than one value.
4
Test with a Sample Row
Add a test row and set its status to a trigger value → verify the account appears in Thread →
delete the test.
Workflow Example
Thread reacts to page creation and property changes. Edits to a page’s body content alone don’t
fire the trigger — the status property is what moves an account.
Knowledge base mode & agent tools
Connected agents get Notion tools regardless of mode: search and query databases, read pages (including long page content and block structure), and read comments. Write tools — creating pages, updating properties, appending blocks, adding comments — are approval-gated like every state-changing action. Access is bounded by which pages and databases you shared with Thread during the Notion authorization.Notion Database Setup
Recommended Structure
Required columns:- Company Name (text)
- ARR (number, format: currency)
- Close Date (date)
- Primary Contact Email (text/email)
- AE Email (text/email)
- Industry (select)
- Company Size (select)
- Use Case (text/long text)
- Notes (text/long text)
- Status (select: New, In Progress, Complete)
Column Types
Best Practices
Standardize Format
Use consistent company naming and data formats
Required Fields First
Ensure all required fields filled before adding row
Rich Notes Column
Detailed notes → Better Handover Brief drafts
Status Column
Track which rows have been processed
Archive Old Rows
Move completed accounts to archive database
Document Process
Train ops team on required fields and format
Troubleshooting
'Database Not Found' Error
'Database Not Found' Error
Cause: Thread doesn’t have access to databaseSolution: Reconnect and grant access to specific database
Account Not Created from Row
Account Not Created from Row
Cause: The status property didn’t hit a configured trigger value, or the row is in a
different databaseSolution: Verify the database selection, the status property, and the trigger values in
the connector setup — and remember content-only edits don’t trigger
Wrong Data in Account
Wrong Data in Account
Cause: The row is missing the fields Thread expects (company name, contact emails)Solution: Fill the recommended columns; richer rows extract better
Next Steps
Building workflows
Route auto-created accounts down the right path
HubSpot Integration
Alternative CRM integration