> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scoutos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect Notion to Scout: Agents That Read and Write Your Knowledge Base

> Integrate Notion with Scout so agents can search pages and databases, create documentation, and update records across your knowledge base.

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.

<Note>
  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](/databases/sources).
</Note>

## What Scout Agents Can Do in Notion

| Capability                     | Example                                                         |
| ------------------------------ | --------------------------------------------------------------- |
| **Search pages and databases** | Find existing runbooks or project briefs to avoid duplicates    |
| **Create new pages**           | Auto-generate incident reports, meeting notes, or decision logs |
| **Update database entries**    | Add rows to a project tracker or update status fields           |
| **Read structured content**    | Pull context from a Notion database to inform responses         |

## How to Connect Notion

<Steps>
  <Step title="Connect Notion to Scout">
    Go to [studio.scoutos.com/integrations](https://studio.scoutos.com/integrations), find **Notion**, and click **Connect**. You'll be redirected to Notion's authorization page.
  </Step>

  <Step title="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.

    <details>
      <summary>What permissions does Scout request?</summary>

      | Permission     | What it's for                          |
      | -------------- | -------------------------------------- |
      | Read content   | View page content and database entries |
      | Insert content | Create new pages and add database rows |
      | Update content | Edit existing pages and modify entries |

      Scout only accesses the pages and databases you explicitly share, and you can adjust what's shared at any time.
    </details>
  </Step>

  <Step title="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

    ```markdown theme={null}
    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.
    ```
  </Step>
</Steps>

## 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

<Steps>
  <Step title="Test searching">
    In Scout chat, ask your agent to search Notion for a topic you know exists. Confirm it returns the right page.
  </Step>

  <Step title="Test creating a page">
    Ask the agent to create a test page, then verify it appears in Notion with the expected content.
  </Step>

  <Step title="Test updating a database">
    Ask the agent to update a database entry and confirm the change in Notion.
  </Step>
</Steps>

## Troubleshooting

<details>
  <summary>Agent can't find a page or database</summary>

  Open the page or database in Notion, click **Share**, and make sure the Scout integration has access. If it still doesn't appear, disconnect and reconnect Notion in [studio.scoutos.com/integrations](https://studio.scoutos.com/integrations) to re-select which pages and databases Scout can see.
</details>

<details>
  <summary>I connected Notion but my agent doesn't see Notion tools</summary>

  1. Go to your agent's **Tools** tab and make sure the Notion tool is toggled **on**
  2. Confirm Notion shows as **Connected** in [studio.scoutos.com/integrations](https://studio.scoutos.com/integrations)
  3. If it's still missing, try reconnecting
</details>

<details>
  <summary>Agent is creating duplicate pages</summary>

  Add a search step to your instructions so the agent searches for existing pages on the same topic before creating a new one. For example: `"Before creating a page, search for existing pages on the same topic and update one if it exists."`
</details>

<details>
  <summary>Authorization failed or timed out</summary>

  Disconnect Notion, click **Connect** again, and complete the authorization — making sure you select the correct workspace. Pop-up blockers can interrupt the OAuth redirect, so allow pop-ups for Scout if the flow doesn't complete.
</details>

## Next Steps

<CardGroup cols={2}>
  <Card title="Slack" icon="slack" href="/integrations/slack">
    Post the pages and links your agent creates in Notion straight to a Slack channel.
  </Card>

  <Card title="Databases" icon="layer-group" href="/databases/sources">
    Sync Notion content into a database so agents can search it as a knowledge base.
  </Card>

  <Card title="Google Drive" icon="google-drive" href="/integrations/google-drive">
    Pull context from documents and summarize it into Notion pages.
  </Card>

  <Card title="Integrations Overview" icon="grid" href="/integrations/overview">
    See the full integration stack and recommended connection order.
  </Card>
</CardGroup>