DatriseAI-first ETL

Outreach Supabase

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

How Datrise loads Outreach into Supabase

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

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE, so re-runs update only what changed. Optional declarative partitioning for high-volume tables. Datrise lands into a dedicated schema and leaves row-level security to you, so synced tables don't inherit public access by accident.

Ideal for app builders who want CRM data alongside their Supabase product data.

Endpoints

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

Supabase: Postgres platform with auth, storage, and realtime APIs.

How Outreach entities map to Supabase

Outreach entitySupabase objectNotes
sequence activityoutreach_sequence_activitytimestamptz events
pipeline execution metricsoutreach_pipeline_execution_metricsid PK · linked to outreach_sequence_activity
sales engagement eventsoutreach_sales_engagement_eventstimestamptz events

FAQ

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

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

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

It runs incrementally — Datrise uses a watermark on updated-at, applied with INSERT … ON CONFLICT DO UPDATE.

Related pipelines

Early access

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