CRM and sales
Zendesk for AI agents.
Managed auth, ready-made tools.
Search, read, create and update Zendesk tickets, and reply to customers, on behalf of each of your users.
About Zendesk
With the Zendesk connector, your agent works with each user’s Zendesk Support: it searches tickets, reads the conversation, opens new tickets, changes status and assignee, replies to customers or adds internal notes, and finds help center articles. Each user connects their own Zendesk account through managed OAuth, and your agent acts with that user’s Zendesk role, within the operations your project allows.
Zendesk is a customer service platform for support tickets, messaging and help centers.
Tools
What your agent can do in Zendesk.
Each tool is a capability the model can call. You decide which ones a project allows, and every call runs with the end user's own Zendesk connection.
-
Search tickets
Readzendesk_search_ticketsFind tickets by keyword, status, requester or other conditions.
-
Get a ticket
Readzendesk_get_ticketRead a ticket's subject, status, priority and assignee.
-
List comments
Readzendesk_list_commentsRead a ticket's conversation, with public replies and internal notes.
-
Create a ticket
Writezendesk_create_ticketOpen a new ticket for a requester.
-
Update a ticket
Writezendesk_update_ticketChange a ticket's status, priority, assignee or tags.
-
Add a comment
Writezendesk_add_commentReply to the requester or add an internal note.
-
Search users
Readzendesk_search_usersFind a customer or agent by name or email.
-
Search articles
Readzendesk_search_articlesFind help center articles that match a question.
No tool matches that search.
Control
Limits you can set.
You decide what your agent may do in Zendesk, and Agent200 runs every call within those limits.
-
Turn single tools on or off
Allow
zendesk_search_ticketsand the other read tools, and switch offzendesk_add_commentif your agent should never reply to customers. -
Restrict what the agent reaches
Choose the endpoints and scopes a project may use. A call outside them is refused.
Get started
Connect Zendesk
in three steps.
-
1
Set up the SDK
Add the Agent200 SDK to the codebase you already have and authenticate with your API key. The key covers every connector enabled for the project.
agent.jsConceptual exampleSet up the SDK with the Agent200 API key // One Agent200 API key covers every connector enabled for the project. const agent200 = new Agent200({ apiKey: process.env.AGENT200_API_KEY, }); -
2
Let your user connect Zendesk
Each end user authorizes their own Zendesk account once. Agent200 runs the OAuth flow, handles the callback, stores the tokens and refreshes them.
connect.jsConceptual exampleLet an end user connect their account (managed OAuth) // Each end user authorizes their own Zendesk account, once. const connection = await agent200 .user("user_123") .connect("zendesk"); if (connection.authorizationUrl) { // Show this link to your user; Agent200 handles the rest. console.log(connection.authorizationUrl); } -
3
Run with the Zendesk tools
Name the user, the model and the tools. The model decides which Zendesk tools to call, and Agent200 executes them with that user's connection.
run.jsConceptual exampleRun a request with the connector's tools const result = await agent200 .user("user_123") .run({ model: "openai/gpt-5.6-sol", input: "Show me the urgent tickets opened today", tools: ["zendesk"], }); console.log(result.output);
Access
Sign-in and permissions.
-
Who signs in
Each of your users, once, on their Zendesk account's own sign-in page. You never see or store their Zendesk password.
-
What access is requested
Read access, and write access when your agent changes tickets, as shown on Zendesk's consent screen. Zendesk's roles still decide what each user can see and change.
For agents
Instructions for AI agents.
Using a coding agent? Paste this brief into it, or give it the address of this page. It describes the Zendesk connector and how to use it.
Connector: Zendesk, through Agent200. In code: "zendesk". What it does: Search, read, create and update Zendesk tickets, and reply to customers, on behalf of each of your users. Page: https://www.agent200.com/tools/zendesk/ 1. Get an Agent200 API key. If the developer has none, send them to https://agent200.com/platform/apikeys/ and ask them to choose "Create an API key". Read the key from the AGENT200_API_KEY environment variable. Never ask for it in chat, and never write it into code, prompts or logs. 2. Sign-in is managed OAuth. Each end user approves access once, on Zendesk's own page, through the authorization link Agent200 returns. Never ask a user for a Zendesk password or token in chat. 3. Give every request a stable id for the end user. Agent200 uses only that user's own connection. 4. Read tools: zendesk_search_tickets, zendesk_get_ticket, zendesk_list_comments, zendesk_search_users, zendesk_search_articles. Write tools: zendesk_create_ticket, zendesk_update_ticket, zendesk_add_comment. Name "zendesk" in the tools of a request; the model decides which tool to call. 5. Stay within the project's settings. If a tool is turned off or a call is refused, tell the user. Do not work around it. 6. Before a write, confirm with the user, unless they asked for that exact change. 7. For setup with a specific framework, follow its guide: https://www.agent200.com/tools/zendesk/framework/claude/ https://www.agent200.com/tools/zendesk/framework/chatgpt/ https://www.agent200.com/tools/zendesk/framework/claude-code/ https://www.agent200.com/tools/zendesk/framework/muse/ https://www.agent200.com/tools/zendesk/framework/grok-bot/ https://www.agent200.com/tools/zendesk/framework/openai-dots/ https://www.agent200.com/tools/zendesk/framework/claude-duet/ https://www.agent200.com/tools/zendesk/framework/hermes-agent/ https://www.agent200.com/tools/zendesk/framework/openclaw/ The code on the connector page is a conceptual example of the SDK. SDK reference: https://docs.igpt.ai/
This page is also available as Markdown, for agents and LLMs: /tools/zendesk.md
Guides
Use Zendesk with the AI you build on.
Step-by-step setup for Zendesk with a specific model, assistant or agent framework.
-
Zendesk + Claude
How to connect Zendesk to Claude
-
Zendesk + ChatGPT
How to connect Zendesk to ChatGPT
-
Zendesk + Claude Code
How to connect Zendesk to Claude Code
-
Zendesk + Muse
How to connect Zendesk to Muse
-
Zendesk + Grok Bot
How to connect Zendesk to Grok Bot
-
Zendesk + OpenAI Dots
How to connect Zendesk to OpenAI Dots
-
Zendesk + Claude Duet
How to connect Zendesk to Claude Duet
-
Zendesk + Hermes Agent
How to connect Zendesk to Hermes Agent
-
Zendesk + OpenClaw
How to connect Zendesk to OpenClaw
FAQ
Zendesk and Agent200, answered.
Who handles the Zendesk OAuth flow and the tokens?
Agent200. It runs the authorization, handles the callback on its own domain, stores the tokens and refreshes them. You do not build or maintain an OAuth integration for Zendesk.
Does my agent act as the end user?
Within what that user authorized, yes. Every request names an end user, and Agent200 uses only that user's Zendesk connection, never another user's. It cannot reach anything the user or Zendesk has not authorized.
Can I limit what my agent can do in Zendesk?
Yes. You choose which services, endpoints and authorization scopes are allowed in your Agent200 configuration, and the agent works only within them.