DatriseAI-first ETL

Zendesk Talk to Sisense Integration

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

How Datrise loads Zendesk Talk into Sisense

Datrise syncs Zendesk Talk's calls, agents, queues, call legs, recordings, and call metrics into Sisense as modeled tables for a Sisense ElastiCube (or live connection). Flexible or custom fields land in flattened columns for the cube, and timestamps such as created, updated, and status changes are typed as date/time fields.

Sync is incremental: Datrise uses incremental ElastiCube builds on changed rows, so re-runs update only what changed. Date-partitioned facts to speed cube builds. ElastiCube is an in-memory model, so Datrise lands incremental, build-friendly tables rather than forcing full rebuilds.

Ideal for embedded analytics on an in-memory engine.

Endpoints

Zendesk Talk: Voice support calls and queue performance.

Sisense: Analytics platform with elastic data models and embedded analytics.

How Zendesk Talk entities map to Sisense

Zendesk Talk entitySisense objectNotes
callszendesk_talk_callsid PK · custom fields → flattened columns for the cube
agentszendesk_talk_agentsid PK · linked to zendesk_talk_calls
queueszendesk_talk_queuesid PK · linked to zendesk_talk_calls
call legszendesk_talk_call_legsid PK · linked to zendesk_talk_calls

FAQ

How does Datrise handle Zendesk Talk's custom fields in Sisense?

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

How does the Zendesk Talk to Sisense sync stay up to date?

It runs incrementally — Datrise uses incremental ElastiCube builds on changed rows.

Related pipelines

Early access

Connect Zendesk Talk to Sisense 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.