Autopilot Activities → Google BigQuery
AI-first ETL from Autopilot Activities into Google BigQuery. Governed entities, incremental sync, typed landing tables.
How Datrise loads Autopilot Activities into Google BigQuery
Datrise syncs Autopilot Activities's records, events, and configuration objects into Google BigQuery as a partitioned table per source entity. Flexible or custom fields land in JSON or nested/repeated (STRUCT) columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP.
Sync is incremental: Datrise uses appends to a staging table, then MERGE on stable id into the partitioned target, so re-runs update only what changed. Partition by ingestion or event date and cluster by entity id to keep scanned bytes low. BigQuery bills by bytes scanned, so Datrise partitions and clusters every table to keep query costs predictable.
Ideal for Google-stack analytics and ML on serverless infrastructure.
Endpoints
Autopilot Activities: SaaS or API data source for analytics and warehouse sync.
Google BigQuery: Serverless analytics warehouse on GCP.
How Autopilot Activities entities map to Google BigQuery
| Autopilot Activities entity | Google BigQuery object | Notes |
|---|---|---|
| records | autopilot_activities_records | id PK · custom fields → JSON or nested/repeated (STRUCT) columns |
| events | autopilot_activities_events | TIMESTAMP events |
| configuration objects | autopilot_activities_configuration_objects | id PK · linked to autopilot_activities_records |
FAQ
How does Datrise handle Autopilot Activities's custom fields in Google BigQuery?
Flexible values are stored as JSON or nested/repeated (STRUCT) columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Google BigQuery types.
How does the Autopilot Activities to Google BigQuery sync stay up to date?
It runs incrementally — Datrise uses appends to a staging table, then MERGE on stable id into the partitioned target.
Related pipelines
More destinations for Autopilot Activities
- Autopilot Activities → Amazon Redshift
- Autopilot Activities → Databricks SQL Warehouse
- Autopilot Activities → ClickHouse
- Autopilot Activities → DuckDB
- Autopilot Activities → Amazon Athena
- Autopilot Activities → Amazon S3 Data Lake
- Autopilot Activities → Azure Data Lake Storage
- Autopilot Activities → Azure Synapse
- Autopilot Activities → Spreadsheets
- Autopilot Activities → Airtable
- Autopilot Activities → CSV Files
- Autopilot Activities → MongoDB
More sources for Google BigQuery
- Aws Cloudtrail → Google BigQuery
- Azure Table Storage → Google BigQuery
- Azureblobstorage → Google BigQuery
- Babelforce → Google BigQuery
- Bigcommerce → Google BigQuery
- Bigquery → Google BigQuery
- Branch → Google BigQuery
- Braze → Google BigQuery
- Breezometer → Google BigQuery
- Bronto → Google BigQuery
- Callrail → Google BigQuery
- Campaign Monitor → Google BigQuery
Early access
Connect Autopilot Activities to Google BigQuery 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.