Zendesk for AI agents

Manage support tickets, macros, and customer conversations. Sign in once through OAuth and every agent you run can use it.

  • Signs in with OAuth
  • Ready to connect
  • Any MCP client
  • No card required

The route from an agent to Zendesk

Once Zendesk is set up in your workspace, any agent you run can reach it: a Spinrun agent, or Claude, ChatGPT and Cursor through one MCP endpoint. Every call passes through the Spinrun gateway, which sorts it by risk and writes it to the activity log.

By default, every change an agent makes in a connected app waits for your approval, on every plan. Enhanced Control adds per-app read, write and destructive rules at the gateway on Free and Pro.

Zendesk in the catalog

Manage support tickets, macros, and customer conversations. · Customer Support

  1. An agent gets a jobFrom chat, a schedule, or your own AI client
  2. Spinrun checks the callSorted as a read, a write or a destructive call
  3. Zendesk does the workThrough the connection you set up in your workspace
  4. Every call is loggedTool, outcome and duration, in one activity log

From Spinrun recipes

Jobs to hand an agent in Zendesk

Each one is a real prompt from a Spinrun recipe or team page, ready to adapt to your own work.

  • “Billing tickets get a billing tag, P0s go straight to on-call, and everything else unassigned in Zendesk is sorted by how urgent it is.”

    Queue sorting

  • “Answer this ticket like we know the customer. Our last month of email with them, the tickets they've opened lately and their tier should all shape the draft.”

    Reply with history

  • “Tell #eng-billing we have a confirmed bug here, and give them a ticket for it in Linear's Billing project.”

    Bug to engineering

  • “Renewals at risk and sudden ticket jumps across our 20 biggest accounts: that's this week's note for #customer-success.”

    Account health note

Three steps

From connection to first call

  1. Connect an app once

    Sign in from your workspace with OAuth or an API key. Spinrun keeps the credential in an encrypted vault, never in an agent's config.

  2. Decide what it may do

    By default, every change an agent makes in a connected app waits for your approval, on every plan. Enhanced Control adds per-app rules for reads, writes and destructive calls on Free and Pro.

  3. Let any agent use it

    Claude, ChatGPT, Cursor or a Spinrun agent reach the app through one MCP endpoint, and every call is written to the same activity log.

What it can do

Every Zendesk action, sorted by risk

Spinrun sorts every Zendesk action into one of three tiers. By default, agents ask before a write; on Free and Pro, the rules you set decide which tiers run.

  • Reads

    Read actions

    Fetch and search. Cannot change anything.

  • Writes

    Write actions

    Create and update. Changes data but does not remove it.

  • Destructive

    Destructive actions

    Delete, revoke, or overwrite. Hard or impossible to undo.

Paired in recipes

Apps agents use with Zendesk

These appear next to Zendesk in Spinrun's templates, recipes and team pages.

Same category

Other Customer Support apps

Other apps in this category that your agents can use.

See every app in this category

Questions about Zendesk

You approve Zendesk in its own sign-in window. Spinrun keeps the token in an encrypted vault, refreshes it before it expires, and you can revoke it in one click.

Put Zendesk to work. Start free.

Connect Zendesk, decide what it may do, and give an agent its first job.

Before anything loads

We would like to switch on analytics, so we can see which pages are worth keeping. Nothing has loaded yet and nothing will until you choose. The cookies that keep you signed in and remember your language are not part of this.

Read the Cookie Policy