DatriseAI-first ETL

Zendesk Sunshine Domo

AI-first ETL from Zendesk Sunshine into Domo. Governed entities, incremental sync, typed landing tables.

How Datrise loads Zendesk Sunshine into Domo

Datrise syncs Zendesk Sunshine's records, events, and configuration objects into Domo as datasets in Domo's cloud store via connector. Flexible or custom fields land in flattened columns for Magic ETL, and timestamps such as created, updated, and status changes are typed as date/time columns.

Sync is incremental: Datrise uses partitioned dataset updates rather than full replaces, so re-runs update only what changed. Domo dataset partitions keyed on load date. Domo stores its own copy of data, so Datrise sends incremental partitions to avoid re-uploading whole datasets.

Ideal for all-in-one cloud BI with built-in ETL.

Endpoints

Zendesk Sunshine: SaaS or API data source for analytics and warehouse sync.

Domo: Cloud BI platform combining data integration and executive dashboards.

How Zendesk Sunshine entities map to Domo

Zendesk Sunshine entityDomo objectNotes
recordszendesk_sunshine_recordsid PK · custom fields → flattened columns for Magic ETL
eventszendesk_sunshine_eventsdate/time columns events
configuration objectszendesk_sunshine_configuration_objectsid PK · linked to zendesk_sunshine_records

FAQ

How does Datrise handle Zendesk Sunshine's custom fields in Domo?

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

How does the Zendesk Sunshine to Domo sync stay up to date?

It runs incrementally — Datrise uses partitioned dataset updates rather than full replaces.

Related pipelines

Early access

Connect Zendesk Sunshine to Domo 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.