Zenloop to GoodData Integration
AI-first ETL from Zenloop into GoodData. Governed entities, incremental sync, typed landing tables.
How Datrise loads Zenloop into GoodData
Datrise syncs Zenloop's surveys, answers, NPS scores, respondents, sentiment labels, and feedback topics into GoodData as warehouse tables GoodData maps into its logical data model. Flexible or custom fields land in flattened columns, and timestamps such as created, updated, and status changes are typed as date dimensions.
Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts. GoodData's LDM maps datasets by keys, so Datrise lands stable primary and foreign id columns to keep the model valid.
Ideal for embedded, multi-tenant analytics.
Endpoints
Zenloop: NPS surveys and customer feedback analysis.
GoodData: Composable analytics platform with headless BI and embedded dashboards.
How Zenloop entities map to GoodData
| Zenloop entity | GoodData object | Notes |
|---|---|---|
| surveys | zenloop_surveys | id PK · custom fields → flattened columns |
| answers | zenloop_answers | id PK · linked to zenloop_surveys |
| NPS scores | zenloop_nps_scores | id PK · linked to zenloop_surveys |
| respondents | zenloop_respondents | id PK · linked to zenloop_surveys |
FAQ
How does Datrise handle Zenloop's custom fields in GoodData?
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 GoodData types.
How does the Zenloop to GoodData sync stay up to date?
It runs incrementally — Datrise uses incremental refresh of the connected tables.
Related pipelines
More destinations for Zenloop
Early access
Connect Zenloop to GoodData 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.