# 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.

- Page: https://www.agent200.com/tools/zendesk/
- Category: CRM and sales
- Authentication: Managed OAuth
- Identifier in code: `zendesk`
- Create an API key: https://agent200.com/platform/apikeys/
- Updated: 2026-11-15

## Instructions for AI agents

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/

## About

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.

## Zendesk tools

- **Search tickets** (`zendesk_search_tickets`, read): Find tickets by keyword, status, requester or other conditions.
- **Get a ticket** (`zendesk_get_ticket`, read): Read a ticket's subject, status, priority and assignee.
- **List comments** (`zendesk_list_comments`, read): Read a ticket's conversation, with public replies and internal notes.
- **Create a ticket** (`zendesk_create_ticket`, write): Open a new ticket for a requester.
- **Update a ticket** (`zendesk_update_ticket`, write): Change a ticket's status, priority, assignee or tags.
- **Add a comment** (`zendesk_add_comment`, write): Reply to the requester or add an internal note.
- **Search users** (`zendesk_search_users`, read): Find a customer or agent by name or email.
- **Search articles** (`zendesk_search_articles`, read): Find help center articles that match a question.

## Limits you can set

**Turn single tools on or off.** Allow `zendesk_search_tickets` and the other read tools, and switch off `zendesk_add_comment` if 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

### Step 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.

File `agent.js`:

```js
// One Agent200 API key covers every connector enabled for the project.
const agent200 = new Agent200({
  apiKey: process.env.AGENT200_API_KEY,
});
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `connect.js`:

```js
// 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);
}
```

(Conceptual example of the Agent200 SDK.)

### Step 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.

File `run.js`:

```js
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);
```

(Conceptual example of the Agent200 SDK.)

## 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.

## Example requests

- "Show me the urgent tickets opened today"
- "Summarize the conversation on ticket 4821"
- "Tell the requester the refund is on its way and mark the ticket solved"
- "Find a help center article about resetting passwords"

## Guides: Zendesk with your AI framework

- [Zendesk + Claude](https://www.agent200.com/tools/zendesk/framework/claude.md): Connect Zendesk to Claude through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Zendesk + ChatGPT](https://www.agent200.com/tools/zendesk/framework/chatgpt.md): ChatGPT cannot send an API key to a custom MCP server, so this guide builds Zendesk into your own agent with OpenAI's models and the Agent200 SDK.
- [Zendesk + Claude Code](https://www.agent200.com/tools/zendesk/framework/claude-code.md): Have Claude Code build a Zendesk agent with the Agent200 SDK: managed OAuth, ready-made tools and one API key.
- [Zendesk + Muse](https://www.agent200.com/tools/zendesk/framework/muse.md): Connect Zendesk to Muse through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Zendesk + Grok Bot](https://www.agent200.com/tools/zendesk/framework/grok-bot.md): Connect Zendesk to Grok Bot through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Zendesk + OpenAI Dots](https://www.agent200.com/tools/zendesk/framework/openai-dots.md): Dots cannot send an API key to a custom MCP server, so this guide builds an always-on Zendesk agent with OpenAI's models and the Agent200 SDK.
- [Zendesk + Claude Duet](https://www.agent200.com/tools/zendesk/framework/claude-duet.md): Connect Zendesk to Claude Duet through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Zendesk + Hermes Agent](https://www.agent200.com/tools/zendesk/framework/hermes-agent.md): Connect Zendesk to Hermes Agent through Agent200's MCP server: managed OAuth, ready-made tools and one API key.
- [Zendesk + OpenClaw](https://www.agent200.com/tools/zendesk/framework/openclaw.md): Connect Zendesk to OpenClaw through Agent200's MCP server: managed OAuth, ready-made tools and one API key.

## FAQ

### 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.

## Related connectors

- [HubSpot](https://www.agent200.com/tools/hubspot.md): Look up and update contacts, companies and deals in your users' HubSpot CRM.
- [Salesforce](https://www.agent200.com/tools/salesforce.md): Query and update accounts, contacts and opportunities in Salesforce.
- [LinkedIn](https://www.agent200.com/tools/linkedin.md): Share posts and read profile details on LinkedIn on behalf of each of your users, where the relevant API permissions are available.
- [Stripe](https://www.agent200.com/tools/stripe.md): Look up Stripe customers, payments and invoices, and create invoices and payment links, on behalf of each of your users.

---

Agent200: https://www.agent200.com/ · API keys: https://agent200.com/platform/apikeys/ · Docs: https://docs.igpt.ai/
