BusyBot

Reference · Credentials

Notion API credentials

Used by 2 BusyBot nodes.

Type notionApi 1 field

The Notion credential holds an integration token created at notion.so/my-integrations. The step that catches almost everyone is the second one: a Notion integration sees nothing until you explicitly share a page or database with it, even though the token is perfectly valid.

Fields

FieldTypeRequiredNotes
Internal Integration Secret
apiKey		 password Yes Your Notion Internal Integration Secret from https://www.notion.so/my-integrations

Getting your credentials

  1. Go to notion.so/my-integrations while signed in.
  2. Create a new internal integration, associate it with the workspace you want, and choose the capabilities it needs — read, update, insert content, and user information if required.
  3. Copy the Internal Integration Secret and paste it into the credential’s API Key field.
  4. Share each page or database with the integration. Open it in Notion, use the connections or share menu, and add your integration by name. Sharing a parent page shares its children.

Permissions and scopes

An integration’s reach is the union of what has been shared with it, intersected with the capabilities selected when it was created. Both matter — a read-only integration cannot write to a page it can see.

Share only the pages the workflow needs. Sharing a top-level page grants the integration everything beneath it.

Troubleshooting

  • object_not_found on a page that exists — the page has not been shared with the integration. This is the single most common Notion setup problem.
  • Insufficient permissions — the integration’s capabilities do not include the operation, for example writing with a read-only integration.
  • validation_error on properties — property names and types must match the database schema exactly, including case.

Frequently asked questions

Why does Notion say the page does not exist?

Because the integration has not been given access to it. Open the page in Notion and add the integration through its connections or share menu — the token being valid is not enough.

Do I have to share every page individually?

No — sharing a parent page grants access to everything beneath it. Share the narrowest parent that covers what the workflow needs.

Internal or public integration?

An internal integration is right for your own workspace and is what this credential expects. Public OAuth integrations are for distributing an app to other workspaces.

Why is a property update rejected?

Property names and types must match the database schema exactly, including case. A mismatch is a validation error rather than a permissions one.

Nodes that use Notion API

One credential works across every node below — create it once and reuse it.

Last updated . Spotted something wrong? Tell us.