DatriseAI-first ETL

Zendesk Metabase

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

How Datrise loads Zendesk into Metabase

Datrise syncs Zendesk's tickets, users, organizations, macros, and satisfaction ratings into Metabase as clean SQL tables Metabase auto-discovers. Flexible or custom fields land in flattened columns for the question builder, and timestamps such as created, updated, and status changes are typed as temporal columns for trends.

Sync is incremental: Datrise uses incremental refresh of the connected tables, so re-runs update only what changed. Date-partitioned facts for large questions. Metabase auto-scans schemas, so Datrise uses readable table and column names so the no-code UI stays self-explanatory.

Ideal for self-serve questions and dashboards for whole teams.

Endpoints

Zendesk: Customer support suite with tickets and knowledge base.

Metabase: Open-source analytics with questions, dashboards, and embedded insights.

How Zendesk entities map to Metabase

Zendesk entityMetabase objectNotes
ticketszendesk_ticketsid PK · custom fields → flattened columns for the question builder
userszendesk_usersid PK · linked to zendesk_tickets
organizationszendesk_organizationsid PK · linked to zendesk_tickets
macroszendesk_macrosid PK · linked to zendesk_tickets

FAQ

How does Datrise handle Zendesk's custom fields in Metabase?

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

How does the Zendesk to Metabase sync stay up to date?

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

Related pipelines

Early access

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