A Notion integration expands what you can do with Notion. You can use Notion integrations to interact with Notion data programmatically, so that you can connect that data to other tools or automate workflows within Notion.
For example, you can build an integration that sends external data to a Notion database, adds an automation widget to a Notion page, or syncs Notion with GitHub issues.
Notion users install integrations to tailor their Notion experience to meet their needs. As part of the installation process, users must share specific Notion pages and databases with the integration.
You can build an internal or a public Notion integration.
By default, all integrations start out as internal integrations.
You can set an integration to public from the integration’s settings page.
An internal integration is tied to a single, specific workspace. Only members within the workspace can use the integration.
An internal integration adds the tools and services that your workspace needs to Notion in a way that's tailored to your people, workflows, and resources.
After an internal integration is added to a workspace, members must give the integration access to the specific pages or databases that they want it to use.
You need Admin level access to a workspace in order to add an internal integration to the workspace.
If you don’t have Admin access to the target workspace, then you can always develop the integration in a personal workspace, and later ask a workspace Admin for help.
Public integrations are built for a broad audience. Any Notion user, in any workspace, can use a public integration. Public integrations follow the OAuth 2.0 protocol to access multiple workspaces.
By default, all integrations start out as internal integrations. You can change an integration from internal to public via the integration’s settings page.
As part of the OAuth flow, you need to add a redirect URI in the public integration’s settings page. After a user authenticates with Notion, they’re pointed to the redirect URI. When they’re redirected, Notion also sends the redirect URI a temporary code as part of the auth flow.
In a public integration’s settings page, you can provide a URL to a Notion template that a user can opt to duplicate as a page in their workspace during OAuth.
Integration capabilities establish what an integration, whether public or private, can access and do in a Notion workspace. These capabilities enforce which API endpoints an integration can call, and what content, comment, and user-related information it can access.
For detailed information on integration capabilities, refer to the reference documentation.
Updated 20 days ago