Manually trigger Notion to BigQuery bulk data syncs
Real-time syncs miss bulk imports and manual refreshes. Notis provides a webhook you can call anytime to trigger a full sync of Notion data to BigQuery, giving you control over when data flows.
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
Event-driven syncs don't catch historical imports or manual overhauls. You need a button to hit when you need a full refresh without waiting for the next scheduled run.
- Full control over when Notion data syncs to BigQuery
- Refresh stale data without waiting for next scheduled run
- Trigger after bulk imports or data corrections
- Pair with scheduled runs for hybrid automation
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 export all Notion page data (IDs, titles, properties, timestamps, creators) to BigQuery.'
- 4Notis will give you a unique webhook URL. Save it somewhere (your notes, Slack, wherever you keep URLs).
- 5When you need a full sync, send an HTTP request to that URL (Notis can show you the exact format).
- 6Notis will run the sync and report when it completes.
Questions about this workflow
Is this different from scheduled syncs?
Yes. Webhooks are on-demand (you trigger manually), while scheduled runs happen automatically on a cron schedule. Use both together for full flexibility.
How do I call the webhook?
Notis gives you a URL. You can call it from curl, Zapier, Make, or any tool that sends HTTP requests. Notis can show you examples.
What data gets synced?
You define what in your setup. Typically: page IDs, titles, properties, timestamps, and creator info.
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.