DatriseAI-first ETL

Freshsales GoodData

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

How Datrise loads Freshsales into GoodData

Datrise syncs Freshsales's leads, contacts, deals, calls, and email activity telemetry 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

Freshsales: CRM by Freshworks with built-in phone and email.

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

How Freshsales entities map to GoodData

Freshsales entityGoodData objectNotes
leadsfreshsales_leadsid PK · custom fields → flattened columns
contactsfreshsales_contactsid PK · linked to freshsales_leads
dealsfreshsales_dealsid PK · linked to freshsales_leads
callsfreshsales_callsid PK · linked to freshsales_leads

FAQ

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

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

Related pipelines

Early access

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