DatriseAI-first ETL

Delighted MySQL

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

How Datrise loads Delighted into MySQL

Datrise syncs Delighted's surveys, responses, scores, and follow-up workflows 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

Delighted: NPS and micro-survey feedback platform.

MySQL: Widely used OSS relational engine (InnoDB).

How Delighted entities map to MySQL

Delighted entityMySQL objectNotes
surveysdelighted_surveysid PK · custom fields → JSON columns
responsesdelighted_responsesid PK · linked to delighted_surveys
scoresdelighted_scoresid PK · linked to delighted_surveys
follow-up workflowsdelighted_follow_up_workflowsid PK · linked to delighted_surveys

FAQ

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