Outreach → Holistics
AI-first ETL from Outreach into Holistics. Governed entities, incremental sync, typed landing tables.
How Datrise loads Outreach into Holistics
Datrise syncs Outreach's sequence activity, pipeline execution metrics, and sales engagement events into Holistics as warehouse tables modeled in Holistics. Flexible or custom fields land in flattened columns for the modeling layer, and timestamps such as created, updated, and status changes are typed as date/time dimensions.
Sync is incremental: Datrise uses incremental refresh of the modeled tables, so re-runs update only what changed. Date-partitioned facts for fast aggregates. Holistics models data as code on top of SQL, so Datrise lands stable column names to keep your models from drifting.
Ideal for as-code BI modeling on a warehouse.
Endpoints
Outreach: Sales execution platform for sequence activity and pipeline outcomes.
Holistics: Self-service BI with modeling layers and scheduled report delivery.
How Outreach entities map to Holistics
| Outreach entity | Holistics object | Notes |
|---|---|---|
| sequence activity | outreach_sequence_activity | date/time dimensions events |
| pipeline execution metrics | outreach_pipeline_execution_metrics | id PK · linked to outreach_sequence_activity |
| sales engagement events | outreach_sales_engagement_events | date/time dimensions events |
FAQ
How does Datrise handle Outreach's custom fields in Holistics?
Flexible values are stored as flattened columns for the modeling layer, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Holistics types.
How does the Outreach to Holistics sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the modeled tables.
Related pipelines
More destinations for Outreach
Early access
Connect Outreach to Holistics 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.