Outreach → Domo
AI-first ETL from Outreach into Domo. Governed entities, incremental sync, typed landing tables.
How Datrise loads Outreach into Domo
Datrise syncs Outreach's sequence activity, pipeline execution metrics, and sales engagement events 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
Outreach: Sales execution platform for sequence activity and pipeline outcomes.
Domo: Cloud BI platform combining data integration and executive dashboards.
How Outreach entities map to Domo
| Outreach entity | Domo object | Notes |
|---|---|---|
| sequence activity | outreach_sequence_activity | date/time columns events |
| pipeline execution metrics | outreach_pipeline_execution_metrics | id PK · linked to outreach_sequence_activity |
| sales engagement events | outreach_sales_engagement_events | date/time columns events |
FAQ
How does Datrise handle Outreach'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 Outreach to Domo sync stay up to date?
It runs incrementally — Datrise uses partitioned dataset updates rather than full replaces.
Related pipelines
More destinations for Outreach
Early access
Connect Outreach 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.