Skip to main content
The notion pack authenticates as an integration, which is Notion’s name for an app. For your own workspace an internal one is enough — a secret to copy, no consent screen — but a new integration can see no pages at all until you connect it to some. That last step is the one that turns a working token into empty results, so it gets a step of its own. The links open in a new tab; this page stays where you left it.
1

Create the integration

Open notion.so/profile/integrations → New integration. Give it a name, pick the workspace, leave the type as Internal, and Save.
The New Integration form: integration name Example App, type Internal, associated workspace Example Workspace, and a Create button.
2

Give it the capabilities the tools use

On the integration’s Configuration tab, under Capabilities, tick:
  • Read content, Update content and Insert content
  • Read comments and Insert comments
  • Read user information — with or without email addresses
Those are the capabilities the pack’s tools declare. Save changes.
The Capabilities section: Read, Update and Insert content ticked, the two comment capabilities unticked, and Read user information including email addresses selected.
The screenshot leaves the comment capabilities off; tick them too if you hand out the comment tools.
3

Copy the secret

Still on Configuration: Internal Integration Secret → Show → Copy. It begins ntn_.
The integration's Configuration tab: name Example App, associated workspace Example Workspace, and a masked Internal integration secret with Refresh and Show links.
The pack reads it on its next call. An internal secret does not expire.
4

Connect it to your pages

Open a page the integration should reach, then ••• in its top-right corner → Connections → search for the integration → Confirm. Every page under that one comes with it, so connecting a top-level page covers its whole tree.The integration’s own Access tab does the same from the other side: Edit access and pick the pages there.Without this, every call succeeds and finds nothing — search returns an empty list, and a page you know exists answers object_not_found.
5

Verify

verify_notion.py
The first line is the integration and the workspace it lives in. The second lists the pages you connected; if it is empty, step 4 has not taken.

Your users’ workspaces

A product whose users each connect their own workspace needs a public integration instead, and each user picks the pages to share on Notion’s own consent screen. Register a public Notion integration has the screens. The route is getting the grant; the pack page shows the credential providers.