Google Directory to Holistics Integration

How Datrise loads Google Directory into Holistics

Datrise syncs Google Directory's users, groups, group members, organizational units, devices, and roles into Holistics as warehouse tables modeled in Holistics. Flexible or custom fields land in flattened columns for the modeling layer, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the modeled tables, so re-runs update only what changed. Date-partitioned facts for fast aggregates. Holistics models data as code on top of SQL, so Datrise lands stable column names to keep your models from drifting.

Ideal for as-code BI modeling on a warehouse.

Endpoints

Google Directory: Workspace user, group, and device directory.

Holistics: Self-service BI with modeling layers and scheduled report delivery.

How Google Directory entities map to Holistics

Google Directory entity	Holistics object	Notes
users	`google_directory_users`	id PK · custom fields → flattened columns for the modeling layer
groups	`google_directory_groups`	id PK · linked to google_directory_users
group members	`google_directory_group_members`	id PK · linked to google_directory_users
organizational units	`google_directory_organizational_units`	id PK · linked to google_directory_users

FAQ

How does Datrise handle Google Directory's custom fields in Holistics?

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

How does the Google Directory to Holistics sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the modeled tables.

Related pipelines

Early access

Connect Google Directory to Holistics 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.