DatriseAI-first ETL

Workday Supabase

AI-first ETL from Workday into Supabase. Governed entities, incremental sync, typed landing tables.

How Datrise loads Workday into Supabase

Datrise syncs Workday's HR, finance entities, organizational structures, and operational events into Supabase as a typed table per source entity in your Supabase Postgres. Flexible or custom fields land in jsonb columns, and timestamps such as created, updated, and status changes are typed as timestamptz.

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning for high-volume tables. Datrise lands into a dedicated schema and leaves row-level security to you, so synced tables don't inherit public access by accident.

Ideal for app builders who want CRM data alongside their Supabase product data.

Endpoints

Workday: Enterprise HR and finance source for operational reporting.

Supabase: Postgres platform with auth, storage, and realtime APIs.

How Workday entities map to Supabase

Workday entitySupabase objectNotes
HRworkday_hrid PK · custom fields → jsonb columns
finance entitiesworkday_finance_entitiesid PK · linked to workday_hr
organizational structuresworkday_organizational_structuresid PK · linked to workday_hr
operational eventsworkday_operational_eventstimestamptz events

FAQ

How does Datrise handle Workday's custom fields in Supabase?

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

How does the Workday to Supabase sync stay up to date?

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

Related pipelines

Early access

Connect Workday to Supabase 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.