Connect a Notion workspace and BeforeQuery indexes its pages and databases — product wikis, internal handbooks, meeting-note databases — into the same searchable knowledge base as your docs. Content is converted to clean markdown, chunked, and embedded, so answers cite the exact Notion page they came from.

Prerequisites

  • A Notion workspace where you can create internal integrations (workspace owner or membership with integration rights).
  • A BeforeQuery workspace owner role — only owners can add sources.

Set up the connector

1

Create a Notion internal integration

In Notion, go to Settings → Connections → Develop or manage integrations and create a new internal integration. Copy the integration token (starts with ntn_).
2

Share content with the integration

Notion integrations can only see pages that are explicitly shared with them. Open the top-level page (or database) you want indexed, click ••• → Connections, and add your integration. Sub-pages are included automatically.
3

Add the source in BeforeQuery

In the dashboard at app.beforequery.com, open your Project → Sources, click Add source, and choose Notion. Paste the integration token.Optionally narrow what gets indexed:
  • Root page — index only that page’s subtree.
  • Database — index the pages of a single database.
Leave both empty to index everything shared with the integration.
4

Start the first sync

Click Add. The first sync starts automatically — watch progress on the source card. When it finishes, indexed pages appear under Documents and are immediately answerable in the Playground.

Connection settings

Keeping content in sync

  • Manual — click Sync on the source card any time.
  • Scheduled — set a daily or weekly schedule per source.
  • Change detection re-embeds only pages whose content actually changed.

Troubleshooting

  • Pages missing from the index? The integration probably isn’t connected to them — re-check ••• → Connections on the missing page’s top-level parent.
  • Sync fails with an authorization error? The token was revoked or the integration was removed from the workspace. Generate a new token and update the source.
  • Internal-only content? Mark the indexed documents restricted (see Roles & Permissions) or place the source in an internal-only source group so it never reaches public widget traffic.