DatriseAI-first ETL

Delighted Yellowfin

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

How Datrise loads Delighted into Yellowfin

Datrise syncs Delighted's surveys, responses, scores, and follow-up workflows into Yellowfin as warehouse tables Yellowfin builds views on. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date/time dimensions.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. Yellowfin views reference columns by name, so Datrise lands stable, well-typed columns to keep reports valid.

Ideal for dashboards with automated data storytelling.

Endpoints

Delighted: NPS and micro-survey feedback platform.

Yellowfin: BI suite with dashboards, automated insights, and data storytelling.

How Delighted entities map to Yellowfin

Delighted entityYellowfin objectNotes
surveysdelighted_surveysid PK · custom fields → flattened 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 Yellowfin?

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

How does the Delighted to Yellowfin sync stay up to date?

It runs incrementally — Datrise uses incremental refresh of the connected tables.

Related pipelines

Early access

Connect Delighted to Yellowfin 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.