PlugsightDocs

Zendesk

Connect Zendesk by signing in as yourself, then let your AI search, summarise and answer tickets, add notes and update them with your approval.

Connect Zendesk Support so your AI can search and summarise tickets, count them, and, once you allow it, reply, add internal notes, update tickets, apply macros and open new tickets. You sign in to Zendesk as yourself and click Allow: there are no tokens to copy.

What your AI can do

Your AI works as you, with your Zendesk role's permissions: it sees only what you can see in Zendesk.

Reading

  • Search tickets (zendesk_search_tickets): finds tickets with Zendesk search, for example status:open, requester:jane@acme.com, assignee:me status<solved, tags:refund created>2026-01-01, or plain words. Newest updated first, up to 100 at a time, sorted by updated, created, priority or status.
  • Read a ticket (zendesk_get_ticket): the ticket with its requester, assignee, organisation, custom fields and the whole conversation (public replies and internal notes, oldest first), with links to attachments.
  • Find users (zendesk_find_users): customers or agents by name, email or phone.
  • Ticket counts (zendesk_ticket_stats): how many tickets are new, open, pending, on hold, unsolved and urgent right now, plus how many were created and solved in a period. Can be narrowed with a Zendesk search, such as tags:refund, group:Billing or assignee:me.
  • List macros (zendesk_list_macros): the macros (saved replies and actions) you can use, optionally filtered by words in the title.

Changing (with your approval)

  • Reply or add a note (zendesk_add_comment): a public reply, which Zendesk emails to the requester, or an internal note that only agents see. It can also set the status to open, pending, on hold or solved.
  • Update a ticket (zendesk_update_ticket): status, priority, type, assignee, and adding or removing tags.
  • Apply a macro (zendesk_apply_macro): your AI first previews exactly what the macro will change (its reply text, status, tags and other fields) and shows you, then applies it after your yes.
  • Create a ticket (zendesk_create_ticket): a new ticket for a customer by email (Zendesk adds the person if they're new), with a subject, first message, priority, type, tags and assignee. The first message is an internal note by default, so the customer isn't emailed, unless you ask for it to be sent to them.

Before every change, your AI shows you the exact ticket and the full text or every field change, and waits for your clear yes. It never changes anything on its own initiative.

Try asking:

  • "What are the top five reasons for tickets this week?"
  • "Summarise everything this customer has raised in the last 90 days."
  • "Which urgent tickets have had no reply for more than a day?"
  • "Draft an internal note on ticket 4821 summarising the issue."
  • "Find tickets tagged 'refund' that are still open."
  • "How many tickets did we solve last week compared with the week before?"
  • "Apply the 'Close and thank' macro to ticket 4821."

What you need

  • A Zendesk Support account, and your Zendesk address (the part before .zendesk.com).
  • A Zendesk login with the agent or admin role. End users (customers) can't be connected.

Connect Zendesk

  1. In app.plugsight.app, go to Connections and click Add connection.
  2. Click the Zendesk tile. The Connect Zendesk page opens.
  3. In Your Zendesk address, type the part before .zendesk.com, as in your browser's address bar when you use Zendesk. Pasting the full address also works.
  4. Click Continue with Zendesk. Your Zendesk opens.
  5. Sign in to Zendesk as yourself (an agent or admin), if you aren't already.
  6. Click Allow.

You come straight back to Connections, with a message such as Connected yourcompany.zendesk.com as Jane Smith (admin), id "yourcompany-zendesk". The id is the name your AI uses for this Zendesk.

Only have an older Zendesk API token? See Connect Zendesk with an API token. Most people don't need it.

What it can and can't change

Replies and updates start off: the connection's switch on Connections says Read-only, and your AI can search and read but not change anything. To allow changes:

  1. On Connections, click the Zendesk connection's switch so it says Can reply & update. This needs the Pro or Agency plan.
  2. Check the MCP server your AI app uses has Allow changes ticked (MCP servers → Edit configuration).
  3. Check nothing is paused on Permissions (neither Pause everything nor the Helpdesk pause).
  4. Check the line under the switch says Ready.

Every reply, note, update, macro and new ticket still needs your yes in the chat, and is listed on Activity. Changes appear in Zendesk as made by you. There's no daily limit for Zendesk changes.

Several Zendesk accounts

You can connect more than one Zendesk. When an MCP server has several, name the one you mean, for example "in the EU support desk".

Troubleshooting

That Zendesk user isn't an agent. Use an agent or admin account.

What it means: you signed in to Zendesk as an end user (customer).

How to fix it: connect again, signing in with an agent or admin login.

Enter your Zendesk address, like yourcompany.zendesk.com.

What it means: Your Zendesk address was empty or couldn't be read.

How to fix it: type the part before .zendesk.com, for example yourcompany.

That isn't a Zendesk address. Enter just your Zendesk address, like yourcompany.zendesk.com.

What it means: what you typed isn't a valid Zendesk address.

How to fix it: check the address in your browser when you use Zendesk, and type the part before .zendesk.com.

Zendesk sign-in failed: …

What it means: Zendesk didn't complete the sign-in. The rest of the message says why, for example You didn't allow access in Zendesk. Click Connect again and allow it, ticking every permission box.

How to fix it: click Continue with Zendesk again and click Allow in Zendesk.

Sign in with Zendesk isn't set up on this server yet. If you already have a Zendesk API token, use that.

What it means: Zendesk sign-in isn't available right now. The Connect Zendesk page then shows Connect with an existing API token instead.

How to fix it: if you have an active Zendesk API token, use it: see Connect Zendesk with an API token. Otherwise, email info@plugsight.app.

Zendesk sign-in expired or was revoked. Reconnect this account in the app.

What it means: Zendesk no longer accepts the connection's sign-in. The connection shows Reconnect needed.

How to fix it: on Connections, click Reconnect and sign in to Zendesk again.

Zendesk refused this action for that agent (…). Ask a Zendesk admin for that permission, or reconnect as an admin.

What it means: your Zendesk role doesn't allow that change. The part in brackets is Zendesk's own reason.

How to fix it: ask a Zendesk admin for the permission, or connect with an admin login.

Zendesk has no ticket or user with that id. Use zendesk_search_tickets or zendesk_find_users to find the right one.

What it means: the ticket or person doesn't exist, or was deleted.

How to fix it: check the ticket number, or ask your AI to search for it.

Helpdesk replies and updates are paused (Permissions page).

What it means: the Helpdesk type is paused.

How to fix it: on Permissions, click Resume next to Helpdesk.

Changes are off for "…". Allow them under Connections first.

What it means: the Zendesk connection's switch says Read-only.

How to fix it: on Connections, click the switch so it says Can reply & update.

The "…" MCP is read-only. Allow changes on the MCP server first (MCP servers page).

What it means: the MCP server your AI app uses has Allow changes unticked.

How to fix it: on MCP servers, open that server, click Edit configuration and tick Allow changes.

Sending email and changing helpdesk tickets are on the Pro plan. Upgrade under Billing to turn write access on.

What it means: your plan is Free, which doesn't include changes.

How to fix it: upgrade under Billing. Your AI can still search, read and count tickets on Free.