DatriseAI-first ETL

Outreach MySQL

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

How Datrise loads Outreach into MySQL

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

Sync is incremental: Datrise uses a watermark on updated-at, applied with INSERT … ON DUPLICATE KEY UPDATE, so re-runs update only what changed. Optional RANGE partitioning by load date. MySQL collation matters for CRM text, so Datrise lands utf8mb4 to preserve emoji and non-Latin characters.

Ideal for operational reporting and app databases already standardized on MySQL.

Endpoints

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

MySQL: Widely used OSS relational engine (InnoDB).

How Outreach entities map to MySQL

Outreach entityMySQL objectNotes
sequence activityoutreach_sequence_activityDATETIME/TIMESTAMP events
pipeline execution metricsoutreach_pipeline_execution_metricsid PK · linked to outreach_sequence_activity
sales engagement eventsoutreach_sales_engagement_eventsDATETIME/TIMESTAMP events

FAQ

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

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

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

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

Related pipelines

Early access

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