DatriseAI-first ETL

PCRecruiter to GoodData Integration

AI-first ETL from PCRecruiter into GoodData. Governed entities, incremental sync, typed landing tables.

How Datrise loads PCRecruiter into GoodData

Datrise syncs PCRecruiter's candidates, positions, companies, activities, pipelines, and placements into GoodData as warehouse tables GoodData maps into its logical data model. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date dimensions.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. GoodData's LDM maps datasets by keys, so Datrise lands stable primary and foreign id columns to keep the model valid.

Ideal for embedded, multi-tenant analytics.

Endpoints

PCRecruiter: Recruiting database for candidate and client relationships.

GoodData: Composable analytics platform with headless BI and embedded dashboards.

How PCRecruiter entities map to GoodData

PCRecruiter entityGoodData objectNotes
candidatespcrecruiter_candidatesid PK · custom fields → flattened columns
positionspcrecruiter_positionsid PK · linked to pcrecruiter_candidates
companiespcrecruiter_companiesid PK · linked to pcrecruiter_candidates
activitiespcrecruiter_activitiesdate dimensions events

FAQ

How does Datrise handle PCRecruiter's custom fields in GoodData?

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

How does the PCRecruiter to GoodData sync stay up to date?

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

Related pipelines

Early access

Connect PCRecruiter to GoodData 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.