Salesloft → Domo
AI-first ETL from Salesloft into Domo. Governed entities, incremental sync, typed landing tables.
How Datrise loads Salesloft into Domo
Datrise syncs Salesloft's cadence activity, conversation signals, and revenue workflow execution 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
Salesloft: Revenue workflow platform for cadences, conversations, and coaching signals.
Domo: Cloud BI platform combining data integration and executive dashboards.
How Salesloft entities map to Domo
| Salesloft entity | Domo object | Notes |
|---|---|---|
| cadence activity | salesloft_cadence_activity | date/time columns events |
| conversation signals | salesloft_conversation_signals | id PK · linked to salesloft_cadence_activity |
| revenue workflow execution | salesloft_revenue_workflow_execution | id PK · linked to salesloft_cadence_activity |
FAQ
How does Datrise handle Salesloft'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 Salesloft to Domo sync stay up to date?
It runs incrementally — Datrise uses partitioned dataset updates rather than full replaces.
Related pipelines
More destinations for Salesloft
Early access
Connect Salesloft 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.