Google Cloud Storage to Birst Integration

How Datrise loads Google Cloud Storage into Birst

Datrise syncs Google Cloud Storage's buckets, objects, prefixes, object metadata, generations, and storage classes into Birst as warehouse tables for Birst's automated star schema. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the source tables Birst ingests, so re-runs update only what changed. Date-partitioned facts. Birst builds its own semantic layer, so Datrise lands conformed, well-keyed tables it can automate against.

Ideal for networked, governed enterprise BI.

Endpoints

Google Cloud Storage: Object storage for files and data lake exports on GCP.

Birst: Cloud BI with networked analytics and enterprise semantic layers.

How Google Cloud Storage entities map to Birst

Google Cloud Storage entity	Birst object	Notes
buckets	`google_cloud_storage_f_buckets`	id PK · custom fields → flattened columns
objects	`google_cloud_storage_f_objects`	id PK · linked to google_cloud_storage_f_buckets
prefixes	`google_cloud_storage_f_prefixes`	id PK · linked to google_cloud_storage_f_buckets
object metadata	`google_cloud_storage_f_object_metadata`	id PK · linked to google_cloud_storage_f_buckets

FAQ

How does Datrise handle Google Cloud Storage's custom fields in Birst?

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

How does the Google Cloud Storage to Birst sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the source tables Birst ingests.

Related pipelines

Early access

Connect Google Cloud Storage to Birst 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.