Google BigQuery to Supabase Integration

How Datrise loads Google BigQuery into Supabase

Datrise syncs Google BigQuery's datasets, tables, views, query jobs, table schemas, and partitions into Supabase as a typed table per source entity in your Supabase Postgres. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning for high-volume tables. Datrise lands into a dedicated schema and leaves row-level security to you, so synced tables don't inherit public access by accident.

Ideal for app builders who want CRM data alongside their Supabase product data.

Endpoints

Google BigQuery: Serverless analytics warehouse on Google Cloud.

Supabase: Postgres platform with auth, storage, and realtime APIs.

How Google BigQuery entities map to Supabase

Google BigQuery entity	Supabase object	Notes
datasets	`bigquery_datasets`	id PK · custom fields → jsonb columns
tables	`bigquery_tables`	id PK · linked to bigquery_datasets
views	`bigquery_views`	id PK · linked to bigquery_datasets
query jobs	`bigquery_query_jobs`	id PK · linked to bigquery_datasets

FAQ

How does Datrise handle Google BigQuery's custom fields in Supabase?

Flexible values are stored as jsonb columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Supabase types.

How does the Google BigQuery to Supabase sync stay up to date?

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.

Related pipelines

Early access

Connect Google BigQuery to Supabase the easy way

Skip brittle scripts and manual exports. Join the waitlist to get a guided setup, AI-assisted mapping, and reliable incremental sync for this integration.