Skip to main content
Notion is where many teams keep their runbooks, project briefs, and decision logs. Connecting it to Scout lets your agents work with that knowledge directly — searching existing pages before drafting new ones, generating incident reports into a database, or pulling structured context to ground a response. Setup takes about five minutes and you’ll switch to Notion once to authorize the connection.
This page covers the Notion integration that lets agents read and write pages and databases as a tool. If you instead want to sync Notion content into a searchable knowledge base, see Databases sources.

​
What Scout Agents Can Do in Notion

CapabilityExample
Search pages and databasesFind existing runbooks or project briefs to avoid duplicates
Create new pagesAuto-generate incident reports, meeting notes, or decision logs
Update database entriesAdd rows to a project tracker or update status fields
Read structured contentPull context from a Notion database to inform responses

​
How to Connect Notion

1

Connect Notion to Scout

Go to studio.scoutos.com/integrations, find Notion, and click Connect. You’ll be redirected to Notion’s authorization page.
2

Authorize in Notion

Choose the workspace you want to connect, then select which pages and databases Scout can access. Click Allow access to finish — you’ll be redirected back to Scout.
3

Enable Notion tools on your agent

  1. Go to your agent’s Settings
  2. Click Add Tool in the Tools section and search for Notion
  3. In your agent’s Instructions, specify which databases and pages it should use
For Notion tasks:

1. When an incident is resolved, create an entry in the Incidents database.
2. Before drafting a new runbook, search existing pages for the same topic.
3. Name new pages as "[Date] - [Topic]" and place them in the correct database.
4. Always return the Notion page URL after creating or updating content.

​
Prompt Examples

These prompts work once Notion is connected and enabled on your agent:
  • “Create a Notion page for this project brief and post the link in Slack.”
  • “Update the incident runbook database with the steps from this thread.”
  • “Find pages about the Q1 roadmap and summarize the key initiatives.”
  • “Check if we already have a runbook for this error type, and create one if not.”

​
Best Practices

  • Scope access appropriately. Share only what the agent needs. A single database is safer and easier to reason about than a whole workspace section.
  • Use databases for structured data. For recurring content like incidents, decisions, or tasks, databases give you a consistent schema and make content far easier to search and filter.
  • Set naming conventions in instructions. Tell the agent how to name pages — for example "[Date] - [Topic]" — and which database to place them in, so content stays organized.

​
Testing Your Integration

1

Test searching

In Scout chat, ask your agent to search Notion for a topic you know exists. Confirm it returns the right page.
2

Test creating a page

Ask the agent to create a test page, then verify it appears in Notion with the expected content.
3

Test updating a database

Ask the agent to update a database entry and confirm the change in Notion.

​
Troubleshooting

​
Next Steps

Slack

Post the pages and links your agent creates in Notion straight to a Slack channel.

Databases

Sync Notion content into a database so agents can search it as a knowledge base.

Google Drive

Pull context from documents and summarize it into Notion pages.

Integrations Overview

See the full integration stack and recommended connection order.