DatriseAI-first ETL

JobAdder DuckDB

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

How Datrise loads JobAdder into DuckDB

Datrise syncs JobAdder's contacts, accounts, deals, activities, and lifecycle 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

JobAdder: Recruiting CRM/ATS for candidates, pipelines, and placements.

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

How JobAdder entities map to DuckDB

JobAdder entityDuckDB objectNotes
contactsjobadder_contactsid PK · custom fields → JSON or STRUCT columns
accountsjobadder_accountsid PK · linked to jobadder_contacts
dealsjobadder_dealsid PK · linked to jobadder_contacts
activitiesjobadder_activitiesTIMESTAMP WITH TIME ZONE events

FAQ

How does Datrise handle JobAdder'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 JobAdder 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 JobAdder 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.