DatriseAI-first ETL

Intercom Domo

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

How Datrise loads Intercom into Domo

Datrise syncs Intercom's conversations, customer attributes, inbox events, and support engagement into Domo as datasets in Domo's cloud store via connector. Flexible or custom fields land in flattened columns for Magic ETL, and timestamps such as created, updated, and status changes are typed as date/time columns.

Sync is incremental: Datrise uses partitioned dataset updates rather than full replaces, so re-runs update only what changed. Domo dataset partitions keyed on load date. Domo stores its own copy of data, so Datrise sends incremental partitions to avoid re-uploading whole datasets.

Ideal for all-in-one cloud BI with built-in ETL.

Endpoints

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

Domo: Cloud BI platform combining data integration and executive dashboards.

How Intercom entities map to Domo

Intercom entityDomo objectNotes
conversationsintercom_conversationsid PK · custom fields → flattened columns for Magic ETL
customer attributesintercom_customer_attributesid PK · linked to intercom_conversations
inbox eventsintercom_inbox_eventsdate/time columns events
support engagementintercom_support_engagementid PK · linked to intercom_conversations

FAQ

How does Datrise handle Intercom's custom fields in Domo?

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

How does the Intercom to Domo sync stay up to date?

It runs incrementally — Datrise uses partitioned dataset updates rather than full replaces.

Related pipelines

Early access

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