DatriseAI-first ETL

Outreach Snowflake

AI-first ETL from Outreach into Snowflake. Governed entities, incremental sync, typed landing tables.

How Datrise loads Outreach into Snowflake

Datrise syncs Outreach's sequence activity, pipeline execution metrics, and sales engagement events into Snowflake as a typed table per source entity. Flexible or custom fields land in VARIANT columns, and timestamps such as created, updated, and status changes are typed as TIMESTAMP_TZ.

Sync is incremental: Datrise uses staged loads merged on stable id with MERGE, so credits scale with change volume, not table size, so re-runs update only what changed. Automatic micro-partitioning, with optional clustering keys on high-cardinality ids. Snowflake upper-cases unquoted identifiers, so Datrise standardizes on lower-case quoted names to keep column references stable.

Ideal for central analytics warehouses feeding BI and AI workloads.

Endpoints

Outreach: Sales execution platform for sequence activity and pipeline outcomes.

Snowflake: Cloud data warehouse with separated compute and storage.

How Outreach entities map to Snowflake

Outreach entitySnowflake objectNotes
sequence activityoutreach_sequence_activityTIMESTAMP_TZ events
pipeline execution metricsoutreach_pipeline_execution_metricsid PK · linked to outreach_sequence_activity
sales engagement eventsoutreach_sales_engagement_eventsTIMESTAMP_TZ events

FAQ

How does Datrise handle Outreach's custom fields in Snowflake?

Flexible values are stored as VARIANT columns, so new fields don't require a migration; strongly-typed fields — dates, numbers, and references — are promoted to native Snowflake types.

How does the Outreach to Snowflake sync stay up to date?

It runs incrementally — Datrise uses staged loads merged on stable id with MERGE, so credits scale with change volume, not table size.

Related pipelines

Early access

Connect Outreach to Snowflake 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.