Customer support
Connecting Zendesk to an Autonomous AI Agent
Zendesk centralizes customer tickets. An Atako agent can sort them, prioritize them, and prepare replies, with access limited to the actions you choose.
Possible workflows
Sorting and prioritizing incoming tickets
The agent lists new tickets with list_tickets or search_tickets, reads their content with get_ticket and get_ticket_comments, then updates status, priority, and tags with update_ticket. An urgent billing ticket no longer sits for three hours in a generic queue before reaching the right human agent, and minor tickets are grouped instead of being handled one by one, out of order, by the support team.
First-line support through macros and the Help Center
For recurring questions, the agent checks the existing macros with list_macros and the Help Center articles with get_article, composes a reply consistent with the company's tone, then adds it to the ticket via update_ticket. Ambiguous cases stay open for a human agent rather than being closed by mistake, out of overconfidence in an automated reply poorly calibrated for that specific case.
Structuring customer organizations
When a new client arrives, the agent creates the corresponding organization with create_organization, mapping its email domain, updates its notes and tags with update_organization, and associates the relevant users with update_user. A clean base then makes it easier to automatically filter tickets by client account, rather than sorting each request one by one without the context of the associated account.
Connector actions
list_tickets
Read. List the account's tickets, sortable and filterable.
search_tickets
Read. Search tickets with Zendesk's query syntax.
get_ticket
Read. Retrieve a ticket: status, priority, assignee.
get_ticket_comments
Read. List a ticket's comments, in chronological order.
list_macros
Read. List the available response macros.
get_article
Read. Retrieve a Help Center article.
list_ticket_fields
Read. List the ticket fields defined in the account.
create_ticket
Write. Create a ticket with a subject and a first comment.
update_ticket
Write. Change status, priority, tags, and add a comment.
create_organization
Write. Create an organization, with email domain mapping.
update_organization
Write. Change an organization's name, domains, notes, or tags.
create_user
Write. Create a user, agent or end customer.
Prerequisites
- Admin role on the Atako company to connect the integration.
- The company's Zendesk subdomain (yourcompany.zendesk.com).
- Agent role at minimum on the Zendesk side, Guide admin for the Help Center.
- API token access enabled in Admin Center before generating the token.
How to connect
- 1
Open Settings, Integrations
An admin selects Zendesk and enters the company's subdomain.
- 2
Enable and generate the token on the Zendesk side
Admin Center, Apps and integrations, APIs, enable Token access, then create a token.
- 3
Paste the email and token into Atako
The field expects the Zendesk agent's email address and the token, separated by a colon.
- 4
Grant access to an agent
You choose the precise actions per agent, in read-only or read-and-write scope.
Why Connect an Autonomous Agent to Zendesk
Zendesk centralizes customer requests, along with their history, priority, comments, and the organization they belong to. An autonomous agent with access to it decides on its own, depending on the instruction it receives, to search for a ticket, prioritize it, or prepare a reply, through tool calling.
The connection uses an API key, an email address, and a token combined, with a Zendesk subdomain specific to your account, without ever transmitting the Zendesk account's own password.
This mode of operation suits a support triage agent or a support automation agent well: it runs continuously, receives new tickets as they come in, and prepares the work without waiting for a human to open the Zendesk account in the morning. Zendesk is one of the connectors included in the Standard plan, with no extra cost specific to this integration.
Limits and Best Practices
Zendesk is gradually removing API token authentication in favor of OAuth: tokens inactive for 30 days have been disabled since the end of July 2026, creating new tokens will be blocked at the end of October 2026, and all tokens will stop working on April 30, 2027 (Zendesk announcement). A connection set up today with a token will need to be revisited before that deadline.
The role of the account used to generate the token defines what the token can do on the Zendesk side, in addition to the Atako grant itself: an Agent role is enough for tickets, but managing the Help Center requires a Guide admin role on the account.
The documentation doesn't mention a rate limit specific to the connector, unlike the documented quotas on the email or webhook channels. Every call, whether successful or refused, stays visible in the agent page's audit log. As with every Atako connector, the connection alone grants no access: an admin still has to select the precise actions and scope, agent by agent, before anything runs.
Related use cases
Related integrations
Frequently asked questions
Can the agent close or reply to a ticket without validation?
If it has the update_ticket grant with write scope, yes, it can change the status and add a comment directly. Many companies limit this grant to simple tickets and leave sensitive cases to a human agent.
How do you revoke Atako's access to Zendesk?
From Settings, Integrations, click Revoke on the Zendesk connection. The encrypted token is deleted immediately, and every agent that was using it loses access right away.
Is Zendesk phasing out API token authentication?
Yes, Zendesk is gradually removing API tokens in favor of OAuth, with full deactivation planned for the end of April 2027. A connection set up today with a token will need to be revisited before that deadline.
What to read next
Sources
- Managing API token access to the Zendesk API · accessed on September 4, 2026
- Announcing the removal of API tokens as an authentication method for API requests · accessed on September 4, 2026
- Migrating from API tokens to OAuth access tokens · accessed on September 4, 2026
CTO at Atako
This content was written by Atako's AI agents, then reviewed, corrected, and approved by Romain Laodicina, CTO of Atako.