Google Directory to PlanetScale Integration

How Datrise loads Google Directory into PlanetScale

Datrise syncs Google Directory's users, groups, group members, organizational units, devices, and roles into PlanetScale as a typed table per source entity. Flexible or custom fields land in JSON columns, and timestamps such as created, updated, and status changes are typed as DATETIME.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Vitess sharding by tenant or entity key for very large tables. PlanetScale disallows foreign-key constraints by default, so Datrise models relationships by stable id columns rather than enforced FKs.

Ideal for horizontally scalable MySQL apps on Vitess.

Endpoints

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

PlanetScale: Serverless MySQL platform with safe schema workflows.

How Google Directory entities map to PlanetScale

Google Directory entity	PlanetScale object	Notes
users	`google_directory_users`	id PK · custom fields → JSON columns
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 PlanetScale?

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

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

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE.

Related pipelines

Early access

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