{/* Generated by scripts/generate-integration-catalog.mjs. Do not edit by hand. */}
At a glance
- Availability: Enabled by default.
- Authentication: OAuth 2.0.
- Connection: A user authorizes the connection in the provider's consent screen.
Credentials
Set these per environment. See Connect an integration.
These variables are required only when you supply your own OAuth app. If a managed app is available, you can connect without setting them. Provider permissions and consent still apply.
Setup
- Choose who owns the Notion OAuth app: On hosted Veryfront, Notion uses the Veryfront-managed Notion OAuth app: connect Notion from the project's integrations and approve the Notion consent screen, no environment variables needed. Set NOTION_CLIENT_ID and NOTION_CLIENT_SECRET only to use your own Notion OAuth app, which is required for local and self-hosted runs.
- Create a public integration: In Notion's integration settings, create a public integration and choose the content capabilities the tools need (read, update and insert content).
- Set the redirect URIs: Add the redirect URI of the environment that completes the flow: https://api.veryfront.com/oauth/callback/notion for hosted Veryfront, or your app origin followed by /api/auth/notion/callback for a local or self-hosted app. Set NOTION_CLIENT_ID and NOTION_CLIENT_SECRET from the app's credentials.
- Verify access: Run Search Notion (read-only). It returns pages the user shared during consent without changing them.
Provider notes
- Notion has no OAuth scopes: the integration's capabilities decide what it can do, and during consent the user picks the pages it can reach. The tools see only those pages.
- Tools that create, update, send or delete data are marked as writes and need write authority; the other tools are read-only.
Tools
Verify the connection
Call a read tool such as notion__search_notion with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.