Notion Marketplace

Productivity

Notion Labs, Inc. · Productivity & collaboration suites

Best for: Tools that sync, automate, or enrich content in Notion workspaces.

Overview

Notion integrations connect external services to Notion pages and databases. Internal integrations use API tokens for a single workspace; public integrations use OAuth 2.0 with capability-scoped permissions. Notion also supports embeds and widgets inside pages.

How to build & ship

  1. 1Create an integration at notion.so/my-integrations and start as an internal integration
  2. 2Build against the Notion REST API (or use link-preview/data features) and test in a workspace
  3. 3Convert the integration to a public integration and configure OAuth 2.0 with redirect URIs
  4. 4Set the requested capabilities/scopes and installation scope to 'any workspace' for marketplace eligibility
  5. 5Submit the integration for Notion's security review and complete the directory listing form

Key APIs & SDKs

Notion REST API
OAuth 2.0 authorization
Link Preview integrations
Webhooks / event subscriptions
Official Notion SDK for JavaScript (@notionhq/client)

Integration types

Authentication & security

  • Primary auth: OAuth 2.0
  • Also supports: API key
  • Security review: Not required
  • No formal review for OAuth integrations; public integrations must comply with brand and data policies.
  • Public integrations must pass a Notion security review (and, for link previews, a submission form) before being listed in the integrations directory; timelines depend on the review queue.
  • Rate limits scale with workspace plan; integration tier available.

Monetization

Onboarding
$0
Commission
0%
Merchant of Record
Developer is MoR

Pros & cons for builders

Pros

  • Large, fast-growing base of Notion workspaces and highly engaged users
  • Clean, well-documented REST API with a straightforward OAuth flow
  • Curated directory lends credibility to listed integrations
  • Low barrier to prototype via internal integrations before going public

Cons

  • API surface is comparatively limited (block/database model constraints, rate limits)
  • Directory listing is curated/subset-only, so discovery isn't guaranteed
  • No native paid-billing/monetization layer inside the platform