DatriseAI-first ETL

Workday DuckDB

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

How Datrise loads Workday into DuckDB

Datrise syncs Workday's HR, finance entities, organizational structures, and operational events into DuckDB as a typed table per source entity in a DuckDB file. Flexible or custom fields land in JSON or STRUCT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP WITH TIME ZONE.

Sync is incremental: Datrise uses rewrites changed entities into the local database (or Parquet) on each run, so re-runs update only what changed. Hive-partitioned Parquet by load date when exporting. DuckDB is single-writer and embedded, so Datrise produces a consistent file snapshot rather than concurrent streaming writes.

Ideal for local and notebook analytics without standing up a server.

Endpoints

Workday: Enterprise HR and finance source for operational reporting.

DuckDB: In-process analytics database for fast local OLAP.

How Workday entities map to DuckDB

Workday entityDuckDB objectNotes
HRworkday_hrid PK · custom fields → JSON or STRUCT columns
finance entitiesworkday_finance_entitiesid PK · linked to workday_hr
organizational structuresworkday_organizational_structuresid PK · linked to workday_hr
operational eventsworkday_operational_eventsTIMESTAMP WITH TIME ZONE events

FAQ

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

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

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

It runs incrementally — Datrise uses rewrites changed entities into the local database (or Parquet) on each run.

Related pipelines

Early access

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