DatriseAI-first ETL

Workable to Holistics Integration

AI-first ETL from Workable into Holistics. Governed entities, incremental sync, typed landing tables.

How Datrise loads Workable into Holistics

Datrise syncs Workable's candidates, jobs, applications, interviews, offers, and pipeline stages 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

Workable: Recruiting pipeline and candidate evaluation.

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

How Workable entities map to Holistics

Workable entityHolistics objectNotes
candidatesworkable_candidatesid PK · custom fields → flattened columns for the modeling layer
jobsworkable_jobsid PK · linked to workable_candidates
applicationsworkable_applicationsid PK · linked to workable_candidates
interviewsworkable_interviewsid PK · linked to workable_candidates

FAQ

How does Datrise handle Workable'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 Workable to Holistics sync stay up to date?

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

Related pipelines

Early access

Connect Workable 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.