# Notion

> Give an agent access to specific Notion pages and databases — read them, query them, and write new pages.

The Notion connector lets an agent search your workspace, read pages as plain text, query databases, and create or extend pages.

## When to use it

Notion is where teams keep the context an agent otherwise has to be told: specs, meeting notes, project trackers. An agent that can read it stops asking you for background, and can file its output where the rest of the team already looks.

## Connect it

<Steps>

1. **Open Connectors** in [Agent Builder](/docs/build/agent-builder/) and choose Notion.

2. **Sign in and choose what to share.** Notion's consent screen asks which pages the integration may access — this is the access control, and it is on Notion's side.

3. **Bind the connection to the agent.**

</Steps>

<Aside type="caution" title="Empty results usually mean a page was not shared">
  A search that finds nothing is more often a sharing problem than a spelling one.
  If a page was not included when you authorized — or was created afterwards —
  share it with the integration from Notion's own page menu.
</Aside>

## What an agent can do

| Operation | Gated |
| --- | --- |
| Search pages and databases by title | No |
| Read a page as plain text, including nested lists and toggles | No |
| Query a database, filtering on one property | No |
| Create a page under a page or in a database | No |
| Append content to an existing page | No |

Nothing in Notion is gated by default, because none of these operations sends anything outward or deletes data. Creating and appending do change your workspace — the agent is instructed to confirm the location and title with you first, but the [approval](/docs/work/approvals/) gate does not stop it.

## Working with it

- **Search first.** An agent needs a page's identifier before it can read or extend it, so a vague *"update the roadmap page"* costs a search step. Pasting the page link is faster.
- **Very long pages are truncated.** Reading a page returns as much as fits and says that it was cut. For a large document, point the agent at the section.
- **Database queries filter on one property.** Complex multi-condition views are better built in Notion, with the agent reading the result.

## Limits

- The agent sees only what you shared with the integration in Notion.
- Reading returns plain text. Notion-specific structure — databases inside pages, synced blocks, complex layouts — is flattened, and formatting is not round-tripped exactly.
- There is no delete operation.
- Pages created by the agent are owned by the Notion integration, and appear as such in page history.

## Related

<CardGrid>
  <LinkCard
    title="Connectors overview"
    href="/docs/connect/overview/"
    description="Connection versus binding, and revoking access."
  />
  <LinkCard
    title="Projects"
    href="/docs/capabilities/projects/"
    description="Keeping context in Endue instead of fetching it every time."
  />
  <LinkCard
    title="Available connectors"
    href="/docs/connect/available-connectors/"
    description="Linear, GitLab, and the rest of the catalog."
  />
</CardGrid>