Docs: System guides

Read Zendesk into Maplith

Support tickets, the people who raise them and their organisations, which show what customers need help with and how fast the team answers.

Helpdesk · Also known as Zendesk Support, Zendesk Suite · Checked 2026-10-08

On this page

Best path

Recommended: export files. Zendesk has no official MCP server for reading an account yet, and a small team can have thousands of tickets a month, too many to pass through a chat. The JSON export from Admin Center gives tickets, users and organisations in one go.

Try the paths in this order:

Your agent fetches it, with the access you already gave it. Connectors a vendor or client page confirms: Zendesk plugin in ChatGPT (beta). Your agent checks the tools it already has; if it can reach Zendesk, it looks at a few recent tickets, users and organisations, read-only, and reports which fields and ids are in use.
Maplith reads an MCP server you already run. No official MCP server confirmed. Zendesk has announced an MCP server, but its own documentation does not yet describe one a customer can connect to; community servers exist but are not Zendesk's. Maplith reads a server that serves MCP resources and takes a token a person types under Data sources › Systems, such as one your IT runs for a database.
Export files, the fallback that always works. See the export steps below.

Datasets that make a good map

Dataset	One row is	Key columns	Joins to
Tickets	One support request, with its status, timestamps, group, assignee and custom fields.	ticket id, requester id, organization id, external id, group id, assignee id, status, created at, solved at, custom field values	Users by requester id; Organizations by organization id; shop orders by order number when it is kept in a custom ticket field.
Users	One person in Zendesk: an end user who asks for help, or an agent or admin.	user id, email (Maplith tries to mask it), external id, organization id, role	CRM contacts, shop customers and billing customers by email or by external id when the company sets it.
Organizations	One customer company that users and tickets belong to.	organization id, external id, domain names, created at	CRM companies and accounting customers by external id or email domain; Tickets and Users by organization id.
Ticket comments	One public reply or internal note on a ticket (in the JSON export, not the CSV).	ticket id, author id, public or internal, created at	Tickets by ticket id; Users by author id.

Columns are named, never their values. Maplith tries to mask personal data such as email addresses, but that is best effort: you decide what goes in.

The access to give

Who usually has the rights: An admin. Prefer OAuth with the read scope: Zendesk calls API tokens deprecated, they give broad access to the whole account, and they stop working by 30 April 2027.

Choose the narrowest access that covers the data:

read
tickets:read

Where to click:

Admin Center
Apps and integrations
APIs
OAuth clients
Add OAuth client, fill in the fields and click Save
When the access token is issued, ask for the read scope only

A key or token made here stays in the tool that reads the system, never in a chat. Maplith asks for one only under Data sources › Systems in the app.

Export steps

Format: JSON (CSV for tickets only) Date range: The last three months

One time: the account owner asks Zendesk Customer Support to turn on data exports for the account.
In Admin Center, click Account, then Tools, then Reports, and open the Export tab.
For JSON, pick a date range, choose tickets, users or organizations, and click Export; repeat for each.
For CSV, pick a date range and click Export (tickets only, without comments).
Zendesk emails a link to a zip file when the export is ready, which can take minutes to a day.
These exports are available on some plans only; the API works on all plans.

How much data

About 200–3,000 tickets a month (an estimate). Estimate for a small company, not a measured figure: one support team handling a handful to about a hundred requests a day.

An agent that reads rows through a chat reads every one of them, about one token per four characters. Above a few thousand rows a dataset, or for a daily refresh, an MCP server or an export is the better path.

Always

Read-only, and never a credential sent to Maplith through a chat.
The same recent period, a few months, from every system.
You decide what goes in.

Sources

Written from public documentation, last checked 2026-10-08:

← All system guides · Markdown version