Connect Notion to Google BigQuery in two minutes.
Real-time triggers from Notion, ready-made actions in Google BigQuery. Filter, transform, and route without writing a line of code.
Workflows fire when something happens in Notion.
- New Database ItemWebhook
- New PageWebhook
- Page UpdatedWebhook
Workflows do something in Google BigQuery, instantly.
Pick the way that fits your stack.
Pair pages are mirrored. Each direction gets its own dedicated page.
When something happens in Notion, do it in Google BigQuery.
3 Notion triggers wired to 3 Google BigQuery actions. Most-used pairing: New Database Item → List Datasets.
Or fire it the other way around.
0 Google BigQuery triggers wired to 12 Notion actions downstream.
- Use any trigger in the catalog as the upstream.
Common Notion → Google BigQuery workflows.
Pick a pairing to set it up in two minutes. Each one is a fully editable recipe.
Fires when a new item is added to a Notion database. Common use: mirror submissions into another tracker, send notifications, or run AI enrichment on the new row.
Fires when a new item is added to a Notion database. Common use: mirror submissions into another tracker, send notifications, or run AI enrichment on the new row.
Fires when a new item is added to a Notion database. Common use: mirror submissions into another tracker, send notifications, or run AI enrichment on the new row.
Fires when a new page is created in a Notion database (functionally the same event as Database Item Added; pick whichever name feels natural).
Fires when a new page is created in a Notion database (functionally the same event as Database Item Added; pick whichever name feels natural).
Fires when a new page is created in a Notion database (functionally the same event as Database Item Added; pick whichever name feels natural).
Fires when a page is updated in a Notion database. Combine with property filters to react only to specific transitions (e.g. Status to Done).
Fires when a page is updated in a Notion database. Combine with property filters to react only to specific transitions (e.g. Status to Done).
Fires when a page is updated in a Notion database. Combine with property filters to react only to specific transitions (e.g. Status to Done).
Connect Notion and Google BigQuery in five steps.
No code, no glue, no half-day setup. Each step is one click.
- 1ConnectAuthorize Notion and Google BigQuery
Open Tiny Command, authorize Notion and Google BigQuery once each. Both connections are available to every workflow on your account.
- 2TriggerPick a Notion trigger
Drop the Notion → New Database Item trigger onto the canvas. Tiny Command auto-registers the webhook.
POST /v1/webhooks/notion.trigger-database-item-added - 3TransformAdd a filter or AI step
Optionally add a Filter node ("subject contains URGENT") or an AI step ("classify intent") between trigger and action.
- 4ActionAdd the Google BigQuery action
Drop the Google BigQuery → List Datasets action below it. Map fields from the Notion payload into the Google BigQuery inputs.
bigquery.list-datasets - 5PublishPublish and forget
Hit Publish. Tiny Command runs it in production from second one. Watch the run-log fill up.
Questions about Notion + Google BigQuery.
How long does it take to connect Notion and Google BigQuery on Tiny Command?
Is the Notion ↔ Google BigQuery integration real-time?
Can I filter or transform data between Notion and Google BigQuery?
What Notion events can trigger a Google BigQuery workflow?
Do I need a paid plan to use Notion with Google BigQuery?
What if I want Google BigQuery → Notion instead?
Other apps that pair well with Notion.
Wire Notion to Google BigQuery in 2 minutes.
Free tier available. No credit card. No onboarding call.
