DatriseAI-first ETL

Intercom MySQL

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

How Datrise loads Intercom into MySQL

Datrise syncs Intercom's conversations, customer attributes, inbox events, and support engagement 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

Intercom: Customer messaging platform with CRM-style account and conversation context.

MySQL: Widely used OSS relational engine (InnoDB).

How Intercom entities map to MySQL

Intercom entityMySQL objectNotes
conversationsintercom_conversationsid PK · custom fields → JSON columns
customer attributesintercom_customer_attributesid PK · linked to intercom_conversations
inbox eventsintercom_inbox_eventsDATETIME/TIMESTAMP events
support engagementintercom_support_engagementid PK · linked to intercom_conversations

FAQ

How does Datrise handle Intercom'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 Intercom 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 Intercom 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.