Greenhouse to Qlik Integration

How Datrise loads Greenhouse into Qlik

Datrise syncs Greenhouse's candidates, applications, jobs, interviews, scorecards, and offers into Qlik as tables loaded into Qlik's associative engine (often via QVD). Flexible or custom fields land in flattened columns for the data model, and timestamps such as created, updated, and status changes are typed as date/time fields.

Sync is incremental: Datrise uses incremental QVD loads merged on stable id, so re-runs update only what changed. QVD files per entity and load date. Qlik's associative model joins on identically named fields, so Datrise standardizes key names so associations link correctly.

Ideal for associative, in-memory exploration in Qlik Sense.

Endpoints

Greenhouse: Applicant tracking and structured hiring.

Qlik: Associative analytics with Qlik Sense apps and governed data models.

How Greenhouse entities map to Qlik

Greenhouse entity	Qlik object	Notes
candidates	`greenhouse_candidates`	id PK · custom fields → flattened columns for the data model
applications	`greenhouse_applications`	id PK · linked to greenhouse_candidates
jobs	`greenhouse_jobs`	id PK · linked to greenhouse_candidates
interviews	`greenhouse_interviews`	id PK · linked to greenhouse_candidates

FAQ

How does Datrise handle Greenhouse's custom fields in Qlik?

Flexible values are stored as flattened columns for the data model, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Qlik types.

How does the Greenhouse to Qlik sync stay up to date?

It runs incrementally — Datrise uses incremental QVD loads merged on stable id.

Related pipelines

Early access

Connect Greenhouse to Qlik 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.