Skip to main content
Connect your Notion workspace to let CloudThinker agents search pages and databases, explore structured information, update content, add comments, and organize documentation. Notion authenticates with an internal integration token you create in your Notion workspace. Every content change agents make happens only after you confirm it.

Prerequisites

  • A Notion account with permission to create integrations in the workspace.
  • The pages and databases you want agents to reach, connected to that integration.

Setup

1

Create a Notion integration

Go to notion.so/profile/integrations and create a new internal integration for your workspace. Copy the integration token it generates.
2

Give the integration access to content

In the integration’s settings, open the Access tab and connect the pages and databases agents should reach. You can also connect an individual page from its ••• menu with Connect to integration.
3

Add the connection in CloudThinker

Navigate to Connections → Notion and paste the token into NOTION_TOKEN.Click Connect. CloudThinker verifies the credential and shows a Connected status.

Connection details

Required permissions

The integration’s Capabilities settings in Notion decide what agents can do. Grant only what your workflow needs:
  • Read content is enough for search and summarization.
  • Add Update content and Insert content only if you want agents to edit or create pages — each change still waits for your confirmation in CloudThinker.
Start with a read-only integration — only Read content enabled — and connect only the pages agents genuinely need. Widen later if a workflow requires it.

Agent capabilities

Once connected, agents can:

Verify the connection

Example prompts

Troubleshooting

The token is wrong or was revoked. Copy the current token from your integration’s settings and update the connection.
The page is not connected to the integration. Open the integration’s Access tab and add the page, or connect it from the page’s ••• menu.
The integration lacks the Update content or Insert content capability. Enable it in the integration’s Capabilities settings in Notion, or keep the connection read-only on purpose.

Security

  • Least privilege — grant only the permissions the agents need for your use case; start read-only and widen later.
  • Read-only by default — use read-only credentials unless you want agents to make changes through this connection.
  • Rotate credentials — rotate keys and tokens on your normal schedule; CloudThinker picks up the new value when you update the connection.
  • Revoke on offboarding — remove the credential at the provider when you delete a connection or a teammate leaves.
  • Connect pages deliberately — the integration only sees pages you connect to it, so the Access list is your scope control.
  • Confirmation for edits — agents change Notion content only after you confirm the change.

Knowledge Base

Give agents searchable workspace knowledge inside CloudThinker

Atlassian Connection

Jira and Confluence for issues and docs