Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.pipeshub.com/llms.txt

Use this file to discover all available pages before exploring further.

Notion Logo

Notion

All-in-one workspace and knowledge management

✅ Ready📖 Documentation Available

Overview

The Notion connector syncs pages, databases, and users from your Notion workspace into PipesHub using OAuth 2.0 and a public connection you register in Notion’s developer experience.

What gets synced

EntityDescription
PagesNotion pages you grant during install (and their content)
DatabasesDatabase properties and rows in scope
UsersWorkspace users (when the integration requests email-capable user info)
CommentsComments on shared pages, when enabled on the connection

Authentication

In PipesHub the flow has three tabs: Authenticate Instance (Redirect URL + OAuth client credentials), Authorize (sign in to Notion and pick what to share), then Configure Records (sync strategy and indexing).
This connector matches people by email. Use the same email in PipesHub as in Notion so permissions and visible records line up.

Configuration Guide

You will create a public connection in Notion, copy the Redirect URL from PipesHub into that connection, then finish setup in PipesHub and run Authorize.

How to configure and enable the Notion connector

Step 1: Open Connectors in PipesHub

  1. Open your user profile menu (bottom of the left sidebar) → Workspace Settings.
  2. Under Workspace, select Connectors.
  3. Find Notion and click + Setup.
User profile menu with Workspace Settings
Workspace Connectors page with Notion and + Setup

Step 2: Copy the Redirect URL

On Authenticate Instance, set Instance name, then copy the Redirect URL exactly. You will paste it into Notion in Step 4.
Notion Configuration — Redirect URL to register in Notion

Step 3: Open Notion developer connections

In Notion: Settings & membersFeaturesConnectionsDevelop or manage connections. In the developer area, open BuildPublic connections.
Notion Settings — Connections and Develop or manage connections
Notion developer — Public connections and Create a new connection

Step 4: Create the public connection

  1. Click Create a new connection.
  2. Fill Connection name, optional icon, Development workspace, and Redirect URIs — paste the exact Redirect URL from Step 2.
  3. Choose Installable in (often Any workspace for internal rollout).
  4. Click Create. When the success dialog appears, continue to Configure connection settings.
Notion — New connection form with Redirect URIs
Notion — Connection successfully created

Step 5: Capabilities and OAuth secrets

  1. Under Capabilities, enable at least Read content and Read comments, and choose Read user information including email addresses so PipesHub can map users.
  2. Open the Authorization (OAuth) section. Copy OAuth Client ID and OAuth Client Secret and confirm Redirect URIs still match PipesHub.
Notion connection — Capabilities and user email scope
Notion connection — OAuth Client ID, Secret, and Redirect URIs

Step 6: Finish Authenticate Instance in PipesHub

Return to Notion ConfigurationAuthenticate Instance if you navigated away. Paste Client ID and Client Secret from Step 5, confirm the Redirect URL, then click Next →.
PipesHub Notion Configuration — OAuth credentials on Authenticate Instance

Step 7: Authorize with Notion

  1. On Authorize, click Authenticate Notion to Proceed and complete the browser flow.
  2. Review permissions, choose Select pages, pick teamspaces/pages to share, then Allow access.
PipesHub Notion Configuration — Authorize tab before signing in
Notion — Connect and select pages for the integration
Notion — Choose pages and Allow access
On this Notion screen you choose exactly which content the connector may access: use Search pages, expand Teamspaces or Private, check only the pages and databases you want synced, or use Deselect all and select a smaller set. Whatever you include here is the scope Notion grants the integration Configure Records in PipesHub refines sync and indexing further, but it cannot access pages you never selected. When you are done, click Allow access. When you see Connected – you can continue to Configure records, click Continue to configuration →.
PipesHub Notion Configuration — Authorization success
Authorize with the same email you use in PipesHub. A different account can cause missing pages or permission issues.

Step 8: Configure Records and save

Set Sync strategy and Sync interval, optional Manual indexing, and indexing toggles (for example Index Pages, Index Databases). Add sync filters only if you need to narrow scope. Click Save Configuration.
PipesHub Notion Configuration — Configure Records

Step 9: Start sync

When prompted, choose Start Syncing Now or I’ll do it later. Use Sync Enabled and the sync actions on the instance card as needed.
Notion instance ready to sync confirmation
Open the instance Overview to watch totals, queues, and record types.
Notion connector instance Overview and record stats
Use Re-authenticate with provider on Authorize if tokens are rotated or access was revoked.
  • Notion for developers: https://developers.notion.com/
  • Public OAuth connections: see Notion docs for connections and OAuth under your product version
  • PipesHub: Workspace SettingsConnectorsNotion for the live Redirect URL

Troubleshooting

Common issues

Redirect URI mismatch
  • The value in Notion must exactly match the Redirect URL shown in PipesHub (scheme, host, path, no stray spaces).
Invalid client / secret
  • Regenerate the secret in Notion if needed and paste the new value into Authenticate Instance.
Missing pages after sync
  • Re-run Authorize and expand page/teamspace selection; the connector only sees content you explicitly share.
Email / visibility
  • Confirm the Capabilities user scope includes email and that users sign in to PipesHub with the same address as in Notion.

Data sync behavior

Initial sync

  • Imports pages and databases in the granted scope; duration depends on workspace size.

Incremental sync

  • Runs on your Sync interval when using a scheduled strategy, fetching changes since the last successful run.

FAQ

  1. Email mismatch — Use the same email in PipesHub as in Notion.
  2. Scope — Confirm the right pages were selected during Authorize and that indexing toggles match what you expect.
  3. Still indexing — Open Workspace SettingsConnectorsNotion and check Overview until queues complete.

Ready to get started?

Connect Notion to PipesHub for unified search. Follow the steps above, or contact support if you need help.