Skip to main content
Integrations · Zendesk
Guild agents can read, create, search, and update Zendesk support tickets and customer records. Guild stores your Zendesk OAuth credential server-side and injects it into every request, so agent code never sees it. Every call passes through Guild’s credential proxy, which enforces your access rules and writes an audit trail before anything reaches Zendesk.

Book a demo

See how teams govern agents that use Zendesk.

Talk to sales

Get access to Guild, then connect Zendesk to your first agent.

What the Zendesk integration exposes

Tools cover tickets, ticket comments, ticket fields, views, users, organizations, groups, satisfaction ratings, and search. Agents import them from the @guildai-services/guildai~zendesk package and pick only the operations they need. Guild injects credentials through the connected account.

How it works

1

Open Credentials in Guild

Go to Credentials in Guild and click Connect. Search for and select Zendesk.
2

Enter your subdomain

Type your Zendesk subdomain alone, for example yourcompany, not yourcompany.zendesk.com. Guild accepts only alphanumeric characters and hyphens.
3

Authorize Guild in Zendesk

Sign in to Zendesk and approve Guild’s access. Guild stores the OAuth credential and injects it server-side on every agent request.

Why Zendesk access needs governing

Zendesk credentials can read and write tickets, update statuses, post comments, and query user and organization records. Guild’s credential policies let you write ALLOW and DENY rules the proxy enforces before any request leaves Guild. You can restrict an agent to specific operations such as zendesk_list_tickets and zendesk_show_ticket, block mutating operations with a DENY rule, or scope rules to a single agent or workspace while sharing the same connected credential across others. Guild stores the OAuth token server-side and injects it only after the policy check passes. Agent code, prompts, and containers never see the credential. You can scope a credential to one workspace, one member, or one agent using credential scoping, so a triage agent and an update agent each get only what they need. Agents that cannot reach a credential fail cleanly rather than falling back to a broader one.

About the Zendesk integration

The Zendesk integration gives your agents access to Zendesk support tickets and customer data.

Authentication

  • Type: OAuth 2.0

Setup

1

Open Credentials

Go to Credentials in Guild.
2

Connect Zendesk

Click Zendesk and enter your Zendesk subdomain, such as yourcompany.
3

Authorize Guild

Sign in to Zendesk and approve Guild’s access.
Enter the subdomain alone — yourcompany, not yourcompany.zendesk.com. Guild validates it as a single DNS label, so only alphanumeric characters and hyphens are accepted. See Configuration parameter validation.

OAuth scopes

Scopes Guild requests in the latest published version of guildai~zendesk:

Usage

Selecting specific tools

Agents perform better with fewer tools. Use pick() to include only what your agent needs. Tools are named with the zendesk_ prefix: for example, create_ticket becomes zendesk_create_ticket. A tool’s input is the operation’s path parameters plus its request body’s fields: zendesk_create_ticket takes a ticket object, and zendesk_update_ticket takes ticket_id and a ticket object. Set ticket.comment.public to false to add an internal note the requester doesn’t see.

Tools

Tools in the latest published version of guildai~zendesk:

Webhook events

Zendesk uses a credential-scoped webhook model. When you enable the first Zendesk trigger on a connection, Guild creates a webhook named Guild Webhook in your Zendesk account and routes its events to matching triggers. Disabling the last trigger removes it. Guild checks each delivery’s signature. Zendesk lets only admins manage webhooks, so connect Zendesk as an admin before you enable a trigger. A trigger can narrow the event to one action, such as guild trigger create --type webhook --integration zendesk --event ticket --action comment_added --agent <identifier>. Without an action it fires on all eight actions. Events for the same ticket share one session, so an agent sees a ticket’s history as one conversation. Guild doesn’t filter out changes the agent makes itself. An agent that comments on or updates a ticket fires matching triggers again. The agent acts as the connected Zendesk user, so have it compare the comment’s author.id with that user’s ID and skip its own changes. Connecting a dedicated Zendesk account keeps people’s comments from looking like the agent’s.

Frequently asked questions

Yes. The integration exposes a ticket webhook event with actions including created, comment_added, status_changed, and five others. When you enable the first Zendesk trigger on a connection, Guild creates a webhook named Guild Webhook in your Zendesk account and routes its events to matching triggers. Zendesk requires an admin account to manage webhooks, so connect Zendesk as an admin before enabling a trigger.
No filtering removes changes the agent makes itself. An agent that comments on or updates a ticket fires matching triggers again. The page recommends having the agent compare the comment’s author ID with the connected user’s ID and skip its own changes, or connecting a dedicated Zendesk account so the agent’s activity is distinguishable.
Write a credential policy that allows only the read operations your agent needs, such as zendesk_list_tickets, zendesk_show_ticket, and zendesk_search, and add a DENY rule for any write operations. Guild’s credential proxy enforces these rules before any request reaches Zendesk. See credential policies for rule syntax.
Yes. Credential policy rules accept an agents field that scopes a rule to specific agents. You can allow one agent to create and update tickets while restricting another to read-only operations, all on the same connected Zendesk credential. See credential policies for scoping syntax.

Put a governed agent on Zendesk this week

Book a demo

See how teams govern agents that use Zendesk.

Talk to sales

Get access to Guild, then connect Zendesk to your first agent.
Read: Docs: Credential policies · Credentials · Tools in agents
Last modified on November 4, 2026