Google Directory to Redash Integration

How Datrise loads Google Directory into Redash

Datrise syncs Google Directory's users, groups, group members, organizational units, devices, and roles into Redash as SQL tables Redash queries and visualizes. Flexible or custom fields land in flattened columns for query results, and timestamps such as created, updated, and status changes are typed as temporal columns.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for scheduled queries. Redash caches query results on a schedule, so Datrise keeps tables incrementally fresh so cached dashboards reflect reality.

Ideal for lightweight, query-driven dashboards.

Endpoints

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

Redash: Open-source SQL client for queries, visualizations, and dashboards.

How Google Directory entities map to Redash

Google Directory entity	Redash object	Notes
users	`google_directory_users`	id PK · custom fields → flattened columns for query results
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 Redash?

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

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

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

Related pipelines

Early access

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