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

# Notion

> Connect Rootly AI to Notion — docs, runbooks, and databases — via a single one-click authorization.

## Overview

Notion is a one-click connector that gives Rootly AI read access to your Notion workspace during investigations. When responders need a runbook, an architecture doc, or a past incident write-up, Rootly AI can pull the relevant page directly instead of asking someone to link it.

Every query is **read-only**. Rootly AI can search and read Notion pages and databases but cannot create, comment on, or edit anything on the Notion side.

***

## Before You Start

* **A Notion workspace** with permission to authorize third-party integrations.
* **Read access** to the pages and databases you want Rootly AI to be able to see. Notion permissions are per-page/database, so the connector inherits whatever the authorizing user can see.

***

## Setup

Open **Configuration → AI → Connectors** and click **Connect** on the Notion card. Sign in to Notion and grant Rootly AI access to the workspace and specific pages/databases you want it to be able to read. When the flow completes, the card flips to **Connected**.

<Note>
  Notion's OAuth flow asks you to explicitly grant access to each page or database. If Rootly AI can't find a runbook you expected, the most common cause is that the runbook's parent page wasn't granted access during setup.
</Note>

***

## What Rootly AI Can Read

* **Pages** — full body text of pages you granted access to.
* **Databases** — table rows, filter values, and page content within a database.
* **Runbooks** — any page structured as a runbook, including the checklist blocks Notion supports.
* **Search** — text search across granted content.

<Tip>
  Rootly AI reaches for Notion when a question is about *"how do we handle this?"* — think runbooks, incident playbooks, past retrospective write-ups. Pair with an observability connector so *"how do we handle this?"* has real data behind it.
</Tip>

## During an Incident

*"Here's the runbook for this service, and the last retro that mentioned this failure mode."*

When a responder needs to know how to handle an incident, Rootly AI searches Notion for the affected service's runbook and cites it in the investigation output. It also pulls past retrospectives that mentioned similar failure modes, so recurring issues carry their institutional memory forward instead of being solved from scratch every time.

***

## Best Practices

* **Grant access at a top-level workspace or team page.** Notion access is per-page/database, so a broad grant at the top of a runbooks section is much more useful than clicking through and granting individual pages one at a time.
* **Keep runbook titles descriptive.** Notion search ranks by title match. Descriptive titles ("Payments API on-call runbook — SEV1 response") beat generic ones ("Runbook").
* **Prune stale pages.** If Rootly AI cites an old runbook that's been superseded, archive the old version in Notion so search stops surfacing it.

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="Rootly AI can't find a page I expected" icon="magnifying-glass">
    Most likely cause: the page (or its parent) wasn't granted access during OAuth setup. Notion permissions are explicit — every page Rootly AI can read must have been shared with the integration. Reconnect and grant access to the parent workspace/team page.
  </Accordion>

  <Accordion title="Rootly AI cites the wrong runbook" icon="triangle-exclamation">
    Notion search ranks by title match and recency. A stale page with a strong title match can outrank the current one. Rename or archive outdated pages so search surfaces the right ones.
  </Accordion>

  <Accordion title="Disconnected on the Notion side" icon="plug-circle-xmark">
    If a Notion workspace admin revokes the Rootly AI integration from Notion's side, Rootly's card still shows Connected but every query fails. Reconnect from Rootly to reauthorize.
  </Accordion>
</AccordionGroup>

***

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="Do I have to grant access to every page individually?" icon="key">
    You can grant access at any level of the Notion hierarchy — granting a top-level workspace or team page cascades to its children. Grant broadly at the level where your runbooks live rather than page-by-page.
  </Accordion>

  <Accordion title="Can Rootly AI edit Notion pages?" icon="lock">
    No. Connectors are read-only. Rootly AI can read Notion data but never invoke write actions.
  </Accordion>

  <Accordion title="Does Rootly cache Notion data?" icon="floppy-disk">
    Rootly does not maintain a persistent copy of Notion data — queries run at investigation time and the response is used in reasoning only. Query results *do* appear in the LLM traces Rootly logs for quality monitoring, as with every tool call Rootly AI makes. See [Data Privacy for Rootly AI](/ai/data-privacy-for-rootly-ai) for the retention boundary.
  </Accordion>
</AccordionGroup>

***

## Related Pages

<CardGroup cols={3}>
  <Card title="Connectors Overview" icon="sparkles" href="/ai/connectors/overview">
    All connectors and how they fit together.
  </Card>

  <Card title="Atlassian" icon="jira" href="/ai/connectors/atlassian">
    The other knowledge-management connector — covers Confluence as well as Jira.
  </Card>

  <Card title="Data Privacy for Rootly AI" icon="shield" href="/ai/data-privacy-for-rootly-ai">
    What Rootly AI sees, retention, and model training controls.
  </Card>
</CardGroup>