Skip to content
ClickRuntime

Automate Zendesk

Keep tickets moving without watching the queue. Tag new tickets by topic, warn agents before an SLA is breached, nudge customers on pending tickets and close the ones that went quiet, and get a short report each morning. Describe what you want to your AI assistant, check what it will do, and it keeps running with your laptop closed.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

Create a ClickRuntime automation: give me a link my store can send new orders to. Find the Zendesk user by email, create them if they don't exist, and add the order number, items and total as an internal note on their open tickets.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Ideas

What you can automate in Zendesk

Tickets that tag and summarise themselves, warnings before SLAs slip, pending tickets that get followed up or closed, and reports on what customers struggled with. These are ready-made starting points. Anything else you can describe works too.
The moment it happens

Add new orders to the customer's Zendesk tickets

When a customer places an order, agents see it on their Zendesk profile and as a note on their open tickets.

See how it works
The moment it happens

Turn contact form messages into Zendesk tickets

Messages from your contact form become tickets, without spam or a second ticket for the same question.

See how it works
Every 10 minutesAI

Tag new tickets by topic

Every new ticket gets a topic tag within minutes, so views and reports sort themselves.

See how it works
The moment it happens

Let your voice agent look up callers in Zendesk

Your phone agent gets the caller's Zendesk record and open tickets, or opens a new ticket from the call notes.

See how it works
Daily

Get a daily Zendesk ticket report

Each morning you see how many tickets came in and got solved yesterday, and what's still open by priority.

See how it works
On a schedule

Get an email when a ticket lands in your urgent view

New tickets in the view you care about reach your inbox within five minutes.

See how it works
WeeklyAI

Get a weekly summary of what customers struggled with

Each Monday you get the main themes and pain points from last week's tickets.

See how it works
On a schedule

Get a morning list of tickets open for over 3 days

Each morning you see which tickets have been waiting too long, grouped by assignee.

See how it works
Every 10 minutes

Get warned before tickets breach their SLA

Your team hears about a ticket 30 minutes before it misses its first-reply target, not after.

See how it works
Daily

Solve pending tickets after 2 weeks of silence

Tickets waiting on a customer who never replied are solved automatically, and you get the list.

See how it works
Daily

Nudge customers on pending tickets

Customers who haven't replied in 3 days get one polite reminder on their ticket.

See how it works
Every 15 minutes

Get alerted about bad satisfaction ratings

When a customer rates a ticket bad, your team sees it with their comment within 15 minutes.

See how it works
Hourly

Check suspended tickets so real customers aren't missed

Every hour you get the new emails Zendesk suspended, with the sender and the reason.

See how it works
Every 30 minutesAI

Summarise long tickets in an internal note

When a ticket thread gets long, agents get a short internal summary instead of reading every comment.

See how it works
Weekly

Back up your Zendesk tickets every week

Each week you get a CSV of the tickets that changed, so you have your own copy.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Zendesk, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Zendesk automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Zendesk should do in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every 10 minutes, read new Zendesk tickets, use AI to tag each with a topic like billing, login or shipping, and set priority to urgent if the customer sounds angry.

When a Zendesk ticket has been open for more than 24 hours without a reply, post the ticket number and subject in #support on Slack.

Every Monday, count last week's Zendesk tickets by tag, add the totals to my Support Stats sheet in Google Sheets and email the summary to the team through Gmail.

Works with

Zendesk with the apps you already use

Support work rarely stays in Zendesk. Connect it to the places your team talks, tracks and emails, so the right people hear about a ticket without opening the agent workspace.

Zendesk works with hundreds of other apps

Name any of them when you ask your assistant, and your automation connects them. Over 248 apps are ready to go, and anything with an API works too.

  • Intercom
  • Freshdesk
  • Help Scout
  • Front
  • Gorgias
  • Jira
  • Linear
  • HubSpot
  • Salesforce
  • Shopify
  • Stripe
  • Microsoft Teams
  • Notion
  • Airtable
  • Typeform
  • Outlook
  • Twilio
  • Discord

Beyond chat

Have Zendesk work when you're not in the chat

Connecting Zendesk to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect Zendesk

You connect Zendesk with an API token that a Zendesk admin creates in Admin Center. ClickRuntime signs in as your agent email with that token, so it can only do what that agent can do.

Zendesk

Help desk

  1. In Zendesk Admin Center, go to Apps and integrations, then APIs, then API configuration, and turn on Allow API token access.
  2. Under API tokens, choose Add API token and copy it. Zendesk only shows it once.
  3. Note your Zendesk subdomain (the yourcompany in yourcompany.zendesk.com) and the email of the agent the token should act as.
  4. In the ClickRuntime dashboard, open Connections & secrets and save the token with your subdomain and agent email. It is sent as {email}/token with the token as the password.

Good to know

Zendesk limits that affect automations

  • API rate limits depend on your Zendesk plan, so very large backfills or bulk updates may run more slowly on lower plans.
  • SLA warnings need SLA policies, which Zendesk includes on Professional plans and higher.
  • Satisfaction rating alerts only work if CSAT is turned on in your account.
  • Zendesk has said API tokens will eventually be replaced by OAuth access tokens, so you may need to reconnect when that happens.

FAQ

Questions about automating Zendesk

What can ClickRuntime see and change in Zendesk?
Whatever the agent behind your API token can. It can search and read tickets, views, users, satisfaction ratings and suspended tickets, and it can create tickets, add tags, add public or internal comments and update ticket status.
Does it act on new tickets straight away?
Tickets sent in from your own forms, store or voice agent through a ClickRuntime link are handled the moment they arrive. Automations that watch Zendesk itself, such as tagging, view alerts and SLA warnings, check every 5 to 15 minutes.
Can it warn us before an SLA is breached?
Yes. It checks open tickets against their SLA targets every 10 minutes and alerts you once per ticket when one is within 30 minutes of breaching. This needs SLA policies, available on Zendesk Professional and higher.
Will customers see what it writes?
Only if you ask for it. Summaries and order details are added as internal notes. Follow-up reminders on pending tickets are public comments, and each ticket gets one at most.
Do I need AI for Zendesk automations?
No. Reports, alerts, follow-ups and closing stale tickets run without it. Tagging, long-ticket summaries and the weekly themes report use the AI that comes with every ClickRuntime plan, so you don't need your own AI key.
Is this a Zendesk connector for ChatGPT or Claude?
Not for chatting with Zendesk data. A chat connector lets your assistant read and change Zendesk while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Zendesk event.

Related pages

Keep exploring

Tell your assistant what Zendesk should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude