Zendesk Tools in Macha — The Ones That Actually Need Explaining
When you give a Zendesk agent its tools, most of them do exactly what their names say — add a public reply, update status, assign a ticket. But a few sound similar to each other or are more powerful than they look, and picking the wrong one is a common reason an agent doesn't behave as expected. Here are the ones worth understanding.
Watch the breakdown
The three "get" tools (the usual source of confusion)
This trio trips up almost everyone, because the names are close but they do different things:
Get Ticket — fetches the core ticket: subject, description, status, requester, and comments. This is the workhorse — the main tool for most workflows, since it gives the agent the actual content of the ticket to reason over.
Get Ticket Custom Fields — fetches the values of the custom fields on a specific ticket. If you have a custom field called "Issue Category," this is how the agent reads what's actually in it for the ticket it's looking at. Use this when the agent needs to act on your custom field data.
Get Ticket Fields — lists all the field definitions in your Zendesk, including custom fields (the schema, not the values). It's how an agent learns what fields exist and their options — useful when it needs to set a field and has to know the valid choices.
A quick way to remember it:
- Get Ticket → the ticket's content.
- Get Ticket Custom Fields → the values in this ticket's custom fields.
- Get Ticket Fields → the definitions of all fields (what's available to set).
Why this matters
Give an agent the wrong "get" tool and it'll come up short: ask it to route by your "Issue Category" custom field but only give it Get Ticket, and it won't see the field's value. Give it Get Ticket Custom Fields and it reads exactly what it needs. Matching the tool to the job is the difference between an agent that works and one that's mysteriously missing information.
Powerful write tools to scope carefully
On the write side, most Zendesk tools are clear (add public reply, internal note, update status/priority/tags), but remember they change real things a customer may see. Give an agent only the write tools its job needs, and lean on the read-vs-write distinction to keep it safe — read tools freely, write tools deliberately.
Frequently asked questions
What's the difference between Get Ticket and Get Ticket Custom Fields? Get Ticket fetches the ticket's core content (subject, description, status, comments); Get Ticket Custom Fields fetches the values in that ticket's custom fields.
What does Get Ticket Fields do? It lists the definitions of all your ticket fields (including custom), so the agent knows what fields exist and their valid options.
Which "get" tool should most agents have? Get Ticket, for the ticket content — add Get Ticket Custom Fields if the agent needs your custom-field values.
How do I keep the write tools safe? Give an agent only the write tools its job requires; see read tools vs. write tools.
The bottom line
Most Zendesk tools are self-explanatory; the ones to get right are the three "get" tools — Get Ticket (content), Get Ticket Custom Fields (this ticket's custom-field values), and Get Ticket Fields (the field definitions). Match the tool to what the agent actually needs to read, scope the write tools carefully, and your Zendesk agents will have exactly the right capabilities.
Build a Zendesk agent: give it the right "get" tools and watch it work. 7-day free trial, no credit card required. Start free.
