Skip to content

CRM and sales

Connect Zendesk Support to DataxLand

The Zendesk Support connector reads tickets, per-ticket time metrics, satisfaction ratings, agents, groups and organisations from your Zendesk account. Si maps tickets to the support ticket entity of the standard model, so you get ticket volume, resolution rate, first reply time, resolution time, reopen rate and CSAT right away. Add your orders and you also get tickets per 100 orders, to see which products cause the problems.

Free plan with no time limit · No card required · Sample workspace ready in minutes

What you can do with Zendesk Support

  • Track first reply time and resolution time per group, week by week.
  • Set alerts for when CSAT drops or the reopen rate rises.
  • Count tickets per 100 orders by combining with Shopify, a marketplace such as Shopee, or an orders file.
  • Ask Si which agent resolves the most tickets each day.

What data you get

Each stream lands as its own table in the workspace warehouse, as is; personal-data columns are hashed on load.

Stream (table)Contents
ticketsTickets with status, priority, channel, group, assignee and created and updated times; loaded incrementally.
ticket_metricsFirst reply time, resolution time and reopen count of each ticket.
satisfaction_ratingsCustomer satisfaction ratings (good or bad).
ticket_commentsTicket conversations; they can contain personal details, so select this stream only when you really need it.
usersAgents and customers; name, email and phone are hashed on load.
groupsSupport groups.
organizationsCustomer organisations.

Connection details

Sign-in methodConnection details (API key, account), encrypted at rest
Sync modesFull (reloaded each run) · Incremental (new or changed rows only)
Fields to fill inSubdomain
DeveloperAirbyte (certified), run inside DataxLand
LicenseELv2
Technical docsConnector documentation ↗

Passwords and keys are encrypted at rest. Personal-data columns are hashed on load.

Metrics computed from this source

Real definitions from the analytics packs; dashboards and Si share them.

MetricDefinitionUnit
Support ticketsSupport tickets created in the period (by creation date), any status.Count
Resolved ticketsTickets resolved in the period (by resolution date); status resolved or closed with a resolution timestamp.Count
Resolution rateTickets created in the period that are resolved divided by tickets created in the period.= cs_created_resolved / Support ticketsRatio (%)
Average first response time (hours)Average hours from when the customer created a ticket to the agent's first response, over tickets created in the period that have a response.= cs_first_response_hours_total / cs_responded_ticketsNumber
Average resolution time (hours)Average hours from creation to resolution for tickets resolved in the period.= cs_resolution_hours_total / Resolved ticketsNumber
Ticket reopen rateTickets resolved in the period that were ever reopened divided by tickets resolved in the period.= cs_reopened_tickets / Resolved ticketsRatio (%)
CSAT (satisfaction rate)Share of surveys with a CSAT score of 4 or 5 on a 1-5 scale, among surveys with a valid CSAT score.= cs_csat_positive / Survey responsesRatio (%)
Tickets per agent per dayTickets created in the period divided by agent working days with tickets.= Support tickets / cs_agent_daysNumber
Support tickets per 100 ordersOrder-linked support tickets divided by valid orders, times 100. Shows how many tickets there are for every 100 orders.= Order-linked support tickets * 100 / Valid ordersNumber

Connect Zendesk Support in 4 steps

  1. 1

    Enable an API token

    In Zendesk Admin Center, under Apps and integrations → Zendesk API, enable token access and create a token.

  2. 2

    Add the Zendesk source

    In the workspace choose Add source, find Zendesk Support, enter your subdomain, choose API Token and enter your login email and the token; the token is encrypted at rest.

  3. 3

    Choose streams

    Click Test connection and keep tickets, ticket_metrics, satisfaction_ratings, users and groups.

  4. 4

    Review and build

    Si proposes how tickets map to the customer service model; you approve and build the dashboards.

Limits and caveats

  • Tickets and users contain personal data; name, email and phone columns are hashed on load and never returned through dashboards, the API or MCP.
  • Zendesk limits API calls by plan; a first load of several years of tickets can take hours.
  • Tickets per 100 orders needs an orders source in the same workspace.
  • Requires the Starter plan or above. An Airbyte connector (ELv2) run inside DataxLand.

Frequently asked questions

Can I use OAuth?

The form offers OAuth2.0 with your own client and refresh token; DataxLand does not run the Zendesk sign-in, so an API token is the simplest option.

How is CSAT calculated?

Good ratings divided by all survey responses in the period, following the versioned definition of the customer service pack.

Does it read Zendesk Guide (help center articles)?

The articles streams are available if you select them, but the analytics packs have no standard metrics for help articles yet.

Dashboard templates that use this source

Ask Si about your Zendesk Support data →Zendesk Support + Shopify →All data sources →

Connect Zendesk Support and get verified dashboards

Free plan with no time limit · No card required · Sample workspace ready in minutes