Every claim is tagged: tested, sourced, reported, inferred or unknown. See how

← All guides
Researched guide

Notion

Create a Public connection (integration) in Notion's developer portal to get OAuth credentials. The docs describe no review step for using it; Marketplace listing is separate.

Tier 1 · Self-serve10-25 min hands-onResearched 2026-10-20
DifficultyTier 1 · Self-serve

Inferred Creating a public connection with a redirect URI is self-serve in what we read. But an image caption on Notion's authorization page says the Authorization URL field only 'populates after a public connection is submitted for review', so a review step may sit between creating and using it. Marketplace listing is reviewed separately. [e1]

Your time (hands-on)10-25 min

Inferred Our estimate. No source states a setup time (Composio's guide shows only a 4-minute reading time).

Approval wait5-10 business days

Sourced Only applies if you list on the Notion Marketplace. 5-10 business days is Notion's stated time to hear back; our calendar-day range (7-14) is a conversion. [e5]

Composio managed authAvailable

Sourced Composio's Notion toolkit page lists OAuth2 and API key and says 'Composio-managed OAuth available.' So a developer can connect users without registering their own provider app first; register your own only for your own branding, scopes or rate limits.

Open Composio's toolkit page

Who does what

An agent can

  • Explain field choices and create the Composio auth config once given credentials securely.
  • Test the connection.

You must

  • Sign in and create the connection.
  • Choose installation scope.
  • Store the secret.

Steps

  1. Open the developer portalYouSourced

    Go to the Notion developer portal, Build > Public connections. [e1]

    Why you: Needs your signed-in Notion session.

  2. Create the connectionYouSourced

    Create new connection; set name, development workspace, redirect URI(s), installation scope and capabilities (only what you need). [e1][e2]

    Why you: Needs your signed-in Notion session; scope choice is permanent.

  3. Copy client ID and secretYouSourced

    Open the Configuration tab to get the OAuth client ID and secret. Treat the secret like a password. [e1][e2]

    Why you: Secret must go straight to your secret store.

  4. Create the auth config in ComposioYou or agentSourced

    Create auth config > Notion > OAuth2 > 'Use your own developer authentication' > enter client ID, secret and the same redirect URI. [e2]

Requirements

  • Sourced A Notion workspace to act as the development workspace (Composio's guide says a free workspace is sufficient). [e1][e2]
  • Sourced Required fields: connection name, development workspace, redirect URI(s), installation scope, capabilities. [e1]
  • Sourced Only public connections with installation scope 'Any workspace' can be listed on the Marketplace. The scope cannot be changed after creation, so choose it deliberately. [e3][e6]

Scopes and access

  • Sourced Installation scope is either 'Any workspace' or 'Selected workspaces only' and cannot be changed after creation. Marketplace eligibility depends on choosing Any workspace. [e1]
  • Sourced Access is limited to pages explicitly shared with the integration. [e2]

Review process

  • Sourced Notion reviews every Marketplace listing submission; it sends feedback and you can resubmit. [e4]
  • Sourced Notion says to expect to hear back within 5-10 business days by email. That is a response time, not a guaranteed approval time. [e5]

Gotchas

  • Sourced Pick the installation scope carefully: it cannot be changed after creation. [e1]
  • Sourced Redirect URIs must be HTTPS and exact match: no trailing slash, wildcards or fragments. [e2]
  • Sourced API-key (internal integration) auth only works with Internal integrations; Public integrations must use OAuth. [e2]

If you get stuck

Inferred Connected but the agent cannot see your pages

Likely cause: Notion integrations only see pages explicitly shared with them.

Fix: Share the relevant pages or databases with the integration during authorization or in Notion.

Escalate when: Sharing is blocked by workspace admin settings. [e2]

Next actions

  • Create the public connection (10-25 min).
  • Decide Any workspace vs Selected workspaces before submitting.

What was tested

Nothing here has been tested by hand yet.

What we are unsure about

  • OPEN QUESTION to settle in the first hands-on test: Notion's authorization page has a caption saying the Authorization URL populates after a public connection is submitted for review. We could not tell whether that is a light submission or the full Marketplace review.
  • Notion's portal UI has changed recently (docs point to app.notion.com/developers/connections); third-party screenshots may be stale.
  • The authorization page does not name a privacy-policy requirement; the listing page lists name, description, category, tags, images and logo.
  • No hands-on test logged yet.

Sources

  1. [e1] Notion Developers - Public integrations
    are managed separately through the Listings section
    retrieved 2026-10-20 · quote check: not yet re-matched against the raw page
  2. [e2] Composio - Notion OAuth2 credentials
    Public integrations allow OAuth-based authentication and can be connected by multiple users or workspaces.
    retrieved 2026-10-20 · quote check: not yet re-matched against the raw page
  3. [e3] Notion Developers - Marketplace listing
    Only public connections with an installation scope of Any workspace can be listed on the Marketplace.
    retrieved 2026-10-20 · quote check: not yet re-matched against the raw page
  4. [e4] Notion Developers - Marketplace listing
    The Notion team reviews every listing submission.
    retrieved 2026-10-20 · quote check: not yet re-matched against the raw page
  5. [e5] Notion Developers - Marketplace listing
    expect to hear back from our team within 5-10 business days via email.
    retrieved 2026-10-20 · quote check: not yet re-matched against the raw page
  6. [e6] Notion Developers - Authorization
    Fill out the form with your connection details, including your redirect URI(s) under the OAuth configuration section.
    retrieved 2026-10-20 · quote check: not yet re-matched against the raw page
  7. [e7] Notion Developers - Authorization
    The Authorization URL field populates after a public connection is submitted for review.
    retrieved 2026-10-20 · quote check: not yet re-matched against the raw page
  8. [e8] Composio docs - Notion toolkit, Authentication Details
    Composio-managed OAuth available
    retrieved 2026-10-20 · quote check: not yet re-matched against the raw page

Ask this guide

Questions about the ten library providers are answered from the guides, with the passage each answer rests on. For any other app it researches the web live and says so.

About the builder

Built by Moulshree Bhutra

Founding APM at Vudio.ai, applying for APM, Toolkits at Composio (Bangalore). This prototype is my answer to the take-home: a way for a developer to see the cost of an OAuth app before starting, and to trust what they read.

How I approached the problem

  • Started from what already exists. Composio publishes 46 setup guides. I read ten in full: they cover the clicking, but not setup time, difficulty or the approval wait, which is where teams lose weeks.
  • Designed for one decision. A developer asks "should I start this today?" So effort, wait, and what only you can do come first, and the steps come after.
  • Made trust visible. Every claim is tagged tested, sourced, reported, inferred or unknown, and quotes link to the page they came from. Where no provider states a number, the guide says so instead of guessing.
  • Kept the agent honest in code. The live agent cannot mark anything tested, and a quote it cannot find in a page it actually read is removed. The method page lists what was and was not checked.

Why I am a good fit

  • I have owned a product through integrations and AI. At Vudio.ai I worked across three roles as it grew from a video-commerce tool into an AI marketing platform with 10+ modules, including Shopify-connected widgets and the product side of its Campaign agent.
  • Results I can point to. I contributed to about 7x ARR growth ($30K to $0.2M) over two years through 0 to 1 launches. I redesigned Shoppable Widgets and built self-serve onboarding: activation rose about 74% and turnaround fell from 13 days to 4. I led AI Studio from 0 to 1 (ARPU up 5% among fashion brands) and built an analytics dashboard that lifted free-to-paid conversion about 10%.
  • I build to understand. I have a computer science degree and I prototype my own ideas, so I can talk to engineers about trade-offs. Top 3 of 200+ in NextLeap's Product Management Fellowship.
  • I write down what I do not know. This project lists its own gaps, including that the hands-on registrations are still being run.

Find me

Prototype built for the Composio APM, Toolkits take-home. It never asks for credentials or secrets.