Manually sync Notion search index to BigQuery
Building a searchable content archive from Notion requires manual exports. Notis provides a webhook you can trigger to sync all page content and metadata to BigQuery for full-text search.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Query
Query tool will run a sql query in bigquery. note: make sure the query being input in a single line format. for example, select * from sample dataset.sample table where column name = 'value'
Why this helps
Notion's search is limited to Notion itself. You can't build a searchable archive or analytics on page content without exporting and re-indexing manually.
- Build a searchable archive of all Notion content outside Notion
- Full-text search queries across all pages and databases
- Index metadata for advanced filtering and discovery
- Use BigQuery's powerful search for content you can't find in Notion
Setup
Build it in a few focused steps.
- 1Connect Notion workspace to Notis.
- 2Connect Google BigQuery to Notis.
- 3Ask Notis: 'Create a webhook I can call anytime to sync all Notion page content (titles, body text, metadata, properties) to a BigQuery search_index table.'
- 4Save the webhook URL that Notis provides.
- 5When you want to index or re-index your content, call the webhook.
- 6Query BigQuery for full-text search: 'SELECT * FROM search_index WHERE content LIKE '%keyword%''
Questions about this workflow
Can I index specific databases or just all pages?
You can ask Notis to index all pages or filter to specific databases or spaces.
What metadata gets indexed?
Page title, all properties, body text, creation date, last update, creator email, etc. Customize as needed.
How long does a full sync take?
Depends on workspace size. Notis will report progress so you know when it completes.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Notion to Google BigQuery. A trigger fires from one place; an action lands in another.
Notion triggers
Google BigQuery actions
All Page Events
Triggers when any Notion page is created or updated across the workspace.
Query
Query tool will run a sql query in bigquery. note: make sure the query being input in a single line format. for example, select * from sample dataset.sample table where column name = 'value'
Comment Created
Triggers when a new comment is created in Notion. Optional `page_id` filter scopes to comments on a specific page. When omitted, fires for any new comment in the workspace the integration has access to. Requires the 'Read comments' capability on the Notion integration. If a connection was authorized before that capability was enabled, the user must re-authorize the connection for comment events to flow.
New Comment
Triggers when a new comment is added to a specified Notion block or page.
Database Created
Triggers when a new Notion database (the container) is created. A database is the post-2025-09-03 container that holds one or more data sources. This trigger fires for the container's creation event (`database.created`), distinct from `NOTION_DATASOURCE_CREATED` which fires when a new data source is added to an existing database. Most customers calling Notion's `POST /v1/databases` (the legacy API) or creating a database via the Notion UI will see this event. Adding a new data source to an existing database fires `data_source.created` instead — use `NOTION_DATASOURCE_CREATED` for that. Notion's payload puts `entity.type: "block"` (the container is a `child_database` block in the content tree) and `entity.id` is the database id.
Data Source Created
Triggers when a new Notion data source is created. Fires workspace-wide. The payload's `data.parent` carries the data source's tree parent (typically the teamspace) for downstream filtering. A single template-based database creation can fire multiple `data_source.created` events at once — one per data source the template instantiates.
Data Source Schema Updated
Triggers when a Notion data source's schema is updated. Fires on column add / remove / rename. Payload includes `data.updated_properties: [{id, name, action}]` so consumers can discriminate the kind of change downstream. Optional `data_source_id` filter scopes to schema changes on a single data source. When omitted, fires for any schema change in the workspace the integration has access to. Note: adding a column also fires `page.properties_updated` once per existing row in the data source. Customers wanting a single structural-change signal should use this trigger.
New Page
Triggers when a new page is added to a Notion database.
Page Added to Page
Fires when a new subpage (a `child_page` type block) is added under a specified parent Notion page.
Connect any two apps with Notis in the middle.
Not just Notion and Google BigQuery. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Google BigQuery.