Skip to main content
The Notion tools in Jinba Flow support three connection methods. Pick the one that fits your use case.

​
Internal integration

The classic method: one workspace-wide token.
  1. Visit the Notion Developers page (workspace owner permission required)
  2. Click “New integration”, set a name and the associated workspace, and create it
  3. Copy the Internal Integration Token from the integration settings
  4. In Jinba Flow, go to workspace settings → “Secret” and create a secret of type NOTION_API with the token
  5. In Notion, share the pages/databases your flows need with the integration (”…” menu on the page → “Connections” → add the integration; child pages inherit it)
Only shared pages are accessible. Access survives even if the person who shared them leaves.

​
Personal access token (PAT)

A token each user issues under their own permissions (added by Notion in May 2026). No page sharing is needed — it can access everything its creator can see.
  1. Create a “Personal access token” on the Notion Developers page
  2. Choose an expiration (7 days to 1 year; default 1 year)
  3. Register the token as a secret of type NOTION_API, the same type as an internal integration token
The header format is identical to internal integration tokens, so no extra Jinba Flow configuration is needed. To run flows per-user, combine PATs with personal secrets: each member registers their own PAT as a personal secret (type NOTION_API) and the tool’s Token field is set to “Use personal secret” — each runner’s own PAT is then injected. Notes:
  • Tokens always expire. Re-issue and replace them before the expiration date
  • A token is revoked when its creator leaves the Notion workspace
  • Notion admins can list and revoke PATs, and some plans can restrict who may create them

​
OAuth (public integration)

Users connect by logging in to Notion in the browser. Access is limited to the pages picked on the consent screen’s page picker. Connecting Notion requires an organization-registered Notion OAuth app (organization settings → OAuth apps; only organization OWNERs can configure it). There is no shared app, so Notion does not appear in the connection list until one is registered, and personal connections are not available.

​
Registering the organization OAuth app (organization OWNER)

  1. Create an integration on the Notion Developers page and configure it as a Public integration
    • We recommend “Selected workspaces only” for distribution (fixed at creation time and cannot be changed later)
    • Enable the Read/Update/Insert content capabilities your tools need
  2. In the integration’s OAuth Domain & URIs settings, register the per-organization callback URL shown on Jinba Flow’s organization settings → OAuth apps page as a Redirect URI
  3. Register the integration’s client_id / client_secret in Jinba Flow under organization settings → OAuth apps, provider Notion

​
Connecting as a user

  1. Open the “OAuth” tab from workspace settings → Secret (or the ”+” on a tool’s Token field) and pick Notion
  2. Log in on Notion’s consent screen and use the page picker to select the pages your flows may access
  3. On completion a secret of type NOTION_OAUTH is created. In a Notion tool, select OAuth as the authentication method and choose the secret in the OAuth token field
Notes:
  • Only the pages selected on the consent screen are accessible. To widen access, reconnect, or add the integration from the page’s “Connections” menu in Notion
  • The token is static. If access stops working (e.g. the authorization was revoked), reconnect

​
Using the tools

Notion tools expose separate fields for the two methods: API token uses NOTION_API (internal token / PAT), while OAuth uses NOTION_OAUTH (OAuth connection). See the Notion tools page for details. Note: Treat tokens as sensitive information and never commit them to public repositories.