Skip to main content
This guide shows how to connect Notion to Clarion using a Notion connection (a workspace-scoped bot with its own token — previously called an internal integration).
Estimated time: 5-10 minutes. You need access to:
  • A Clarion workspace
  • A Notion workspace where you are a workspace owner (only workspace owners can create connections)

​
Prerequisites

Before connecting Notion in Clarion, make sure you have:
  • Workspace-owner access in Notion
  • A decision about which pages, wikis, and databases Clarion should be able to read
Notion grants access page by page, not workspace-wide. Clarion can only see content that you explicitly share with the connection. Sharing a top-level page shares everything nested under it.

​
Step 1 - Create a Notion connection

Notion calls these “connections” (previously “internal integrations”) — a bot scoped to your workspace with its own token.
  1. In Notion, go to Settings → Connections → Develop or manage connections. This opens Notion’s Developer portal (app.notion.com/developers).
  2. Click Create a Connection, give it a name (e.g. “Clarion”), and pick the workspace to connect.
  3. In the connection’s Configuration tab, enable the read capabilities:
    • Read content
    • Read user information (name and email is fine)
    Clarion is read-only — you do not need any insert or update capabilities.
  4. Copy the connection’s token from the Configuration tab (it starts with ntn_).
If you set an expiration on the token, note the date — Clarion will lose access when it expires and you will need to paste a fresh token.

​
Step 2 - Share content with the connection

Clarion can only read pages that are shared with the connection. Either:
  • Per page: open a page, click ••• → Connections, and add your new connection. All sub-pages inherit access.
  • In bulk: open the connection in the Developer portal and add pages and databases from its content access settings.
Most teams share their top-level engineering wiki or runbooks page once — everything nested under it becomes readable.

​
Step 3 - Connect Notion in Clarion

  1. In Clarion, go to Integrations.
  2. Open Notion.
  3. Paste the connection token.
  4. Click Connect.
Clarion validates the token and shows the connected Notion workspace name.

​
Step 4 - Verify the connection

After connecting, click Verify. This confirms the token still works and that at least one page is shared with the connection. If verification warns that no pages are shared, go back to Step 2 — the token is valid, but agents will get empty search results until content is shared.

​
How Notion tools use this integration

When Notion tools are enabled, Clarion agents can:
  • Search pages and databases by title. Notion’s API matches titles only, so agents search with distinctive keywords and then read pages in full.
  • Read a page as Markdown, including runbooks, incident docs, and architecture notes.
  • Query databases (data sources) with filters and sorts — useful for runbook tables, service catalogs, and on-call rotations.
  • List workspace members to resolve document owners or mentions.
Clarion never writes to your Notion workspace.

​
Troubleshooting

​
”Notion rejected the token”

  • Check you copied the connection’s full token from its Configuration tab (it starts with ntn_).
  • The token may have expired (if it was created with an expiration) or been revoked. Create a fresh one and reconnect.

​
”The Notion token authenticated but lacks the required read capabilities”

Open the connection in Notion’s Developer portal and enable the read content and read user information capabilities in its Configuration tab. Capability changes take effect immediately.

​
Searches come back empty

The connection has no shared content. Share pages via a page’s ••• → Connections menu or the connection’s content access settings in the Developer portal. Remember access is page-by-page — a valid token alone grants nothing.

​
Enterprise workspaces

Notion Enterprise admins can restrict who may install or add connections. If you cannot add the connection to pages, ask a workspace owner to approve it first.