DatriseAI-first ETL

Salesflare Domo

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

How Datrise loads Salesflare into Domo

Datrise syncs Salesflare's B2B account intelligence, interactions, and automated relationship timelines 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

Salesflare: B2B CRM focused on automation and relationship timeline data.

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

How Salesflare entities map to Domo

Salesflare entityDomo objectNotes
B2B account intelligencesalesflare_b2b_account_intelligenceid PK · custom fields → flattened columns for Magic ETL
interactionssalesflare_interactionsid PK · linked to salesflare_b2b_account_intelligence
automated relationship timelinessalesflare_automated_relationship_timelinesdate/time columns events

FAQ

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

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

Related pipelines

Early access

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