Outreach → Mode
AI-first ETL from Outreach into Mode. Governed entities, incremental sync, typed landing tables.
How Datrise loads Outreach into Mode
Datrise syncs Outreach's sequence activity, pipeline execution metrics, and sales engagement events into Mode as warehouse tables Mode queries with SQL. Flexible or custom fields land in flattened columns for SQL and notebooks, and timestamps such as created, updated, and status changes are typed as temporal columns.
Sync is incremental: Datrise uses incremental refresh of the queried tables, so re-runs update only what changed. Date-partitioned facts for report queries. Mode runs analyst-written SQL, so Datrise lands stable, documented tables that won't break saved reports.
Ideal for SQL-first analysis with Python and R notebooks.
Endpoints
Outreach: Sales execution platform for sequence activity and pipeline outcomes.
Mode: Collaborative analytics workspace for SQL, Python, and shared reports.
How Outreach entities map to Mode
| Outreach entity | Mode object | Notes |
|---|---|---|
| sequence activity | outreach_sequence_activity | temporal columns events |
| pipeline execution metrics | outreach_pipeline_execution_metrics | id PK · linked to outreach_sequence_activity |
| sales engagement events | outreach_sales_engagement_events | temporal columns events |
FAQ
How does Datrise handle Outreach's custom fields in Mode?
Flexible values are stored as flattened columns for SQL and notebooks, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Mode types.
How does the Outreach to Mode sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the queried tables.
Related pipelines
More destinations for Outreach
Early access
Connect Outreach to Mode 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.