DatriseAI-first ETL

Intercom GoodData

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

How Datrise loads Intercom into GoodData

Datrise syncs Intercom's conversations, customer attributes, inbox events, and support engagement 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

Intercom: Customer messaging platform with CRM-style account and conversation context.

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

How Intercom entities map to GoodData

Intercom entityGoodData objectNotes
conversationsintercom_conversationsid PK · custom fields → flattened columns
customer attributesintercom_customer_attributesid PK · linked to intercom_conversations
inbox eventsintercom_inbox_eventsdate dimensions events
support engagementintercom_support_engagementid PK · linked to intercom_conversations

FAQ

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

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

Related pipelines

Early access

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