Outreach → DuckDB
AI-first ETL from Outreach into DuckDB. Governed entities, incremental sync, typed landing tables.
How Datrise loads Outreach into DuckDB
Datrise syncs Outreach's sequence activity, pipeline execution metrics, and sales engagement events into DuckDB as a typed table per source entity in a DuckDB file. Flexible or custom fields land in JSON or STRUCT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP WITH TIME ZONE.
Sync is incremental: Datrise uses rewrites changed entities into the local database (or Parquet) on each run, so re-runs update only what changed. Hive-partitioned Parquet by load date when exporting. DuckDB is single-writer and embedded, so Datrise produces a consistent file snapshot rather than concurrent streaming writes.
Ideal for local and notebook analytics without standing up a server.
Endpoints
Outreach: Sales execution platform for sequence activity and pipeline outcomes.
DuckDB: In-process analytics database for fast local OLAP.
How Outreach entities map to DuckDB
| Outreach entity | DuckDB object | Notes |
|---|---|---|
| sequence activity | outreach_sequence_activity | TIMESTAMP WITH TIME ZONE events |
| pipeline execution metrics | outreach_pipeline_execution_metrics | id PK · linked to outreach_sequence_activity |
| sales engagement events | outreach_sales_engagement_events | TIMESTAMP WITH TIME ZONE events |
FAQ
How does Datrise handle Outreach's custom fields in DuckDB?
Flexible values are stored as JSON or STRUCT columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native DuckDB types.
How does the Outreach to DuckDB sync stay up to date?
It runs incrementally — Datrise uses rewrites changed entities into the local database (or Parquet) on each run.
Related pipelines
More destinations for Outreach
Early access
Connect Outreach to DuckDB 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.