DatriseAI-first ETL

Google Directory to Birst Integration

AI-first ETL from Google Directory into Birst. Governed entities, incremental sync, typed landing tables.

How Datrise loads Google Directory into Birst

Datrise syncs Google Directory's users, groups, group members, organizational units, devices, and roles 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 Directory: Workspace user, group, and device directory.

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

How Google Directory entities map to Birst

Google Directory entityBirst objectNotes
usersgoogle_directory_usersid PK · custom fields → flattened columns
groupsgoogle_directory_groupsid PK · linked to google_directory_users
group membersgoogle_directory_group_membersid PK · linked to google_directory_users
organizational unitsgoogle_directory_organizational_unitsid PK · linked to google_directory_users

FAQ

How does Datrise handle Google Directory'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 Directory 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 Directory 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.