DatriseAI-first ETL

Workable to ClickHouse Integration

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

How Datrise loads Workable into ClickHouse

Datrise syncs Workable's candidates, jobs, applications, interviews, offers, and pipeline stages into ClickHouse as a MergeTree table per source entity. Flexible or custom fields land in JSON or Map columns, and timestamps such as created, updated, and status changes are typed as DateTime64.

Sync is incremental: Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge, so re-runs update only what changed. Partition by month and order by (entity id, updated-at) for fast range scans. ClickHouse deduplicates asynchronously on merge, so Datrise uses ReplacingMergeTree and FINAL-safe queries rather than assuming immediate upserts.

Ideal for high-volume event analytics that need sub-second aggregation.

Endpoints

Workable: Recruiting pipeline and candidate evaluation.

ClickHouse: Columnar OLAP engine for fast aggregations.

How Workable entities map to ClickHouse

Workable entityClickHouse objectNotes
candidatesworkable_candidatesid PK · custom fields → JSON or Map columns
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 ClickHouse?

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

How does the Workable to ClickHouse sync stay up to date?

It runs incrementally — Datrise uses inserts into a ReplacingMergeTree keyed on stable id, so the latest version wins on merge.

Related pipelines

Early access

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