Outreach → GoodData
AI-first ETL from Outreach into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads Outreach into GoodData
Datrise syncs Outreach's sequence activity, pipeline execution metrics, and sales engagement events into GoodData as warehouse tables GoodData maps into its logical data model. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date dimensions.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. GoodData's LDM maps datasets by keys, so Datrise lands stable primary and foreign id columns to keep the model valid.
Ideal for embedded, multi-tenant analytics.
Endpoints
Outreach: Sales execution platform for sequence activity and pipeline outcomes.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How Outreach entities map to GoodData
| Outreach entity | GoodData object | Notes |
|---|---|---|
| sequence activity | outreach_sequence_activity | date dimensions events |
| pipeline execution metrics | outreach_pipeline_execution_metrics | id PK · linked to outreach_sequence_activity |
| sales engagement events | outreach_sales_engagement_events | date dimensions events |
FAQ
How does Datrise handle Outreach's custom fields in GoodData?
Flexible values are stored as flattened columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native GoodData types.
How does the Outreach to GoodData sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Outreach
Early access
Connect Outreach to GoodData 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.