01
One customer, one history
A customer who emailed a ticket last week now messages on WhatsApp. Copilot pulls the Zendesk history into the thread so nobody asks them to explain it twice.
Integrations · Support & ticketing
Zendesk in the conversation.
A helpdesk where email and web support is worked as tickets with an SLA around them. Connect it once and your copilot works with tickets, users, organizations, comments and help-centre articles without leaving the thread — and your workflows can act on it while the customer is still typing.
No credit card required · 7-day free trial
Zendesk
Support & ticketing
01 · COPILOT
Ask for it in plain language. It does the Zendesk part.
Copilot rides inside the inbox. With Zendesk connected it reads tickets, users, organizations, comments and help-centre articles and acts on them from the same panel as the conversation — no second tab, no copying an order number across.
- Search tickets by requester, status, tag or text
- Read a ticket and its full comment history
- Create a ticket from a conversation
- Add a public reply or an internal note to a ticket
- Change status, priority, assignee or tags
- Look up the requester and the organization behind a ticket
What a specific connection exposes is decided by Zendesk, not by us: Settings → Apps lists the real tools your connection carries, each with its own switch.
02 · WORKFLOWS
Something happens in Zendesk. A workflow starts.
Once Zendesk is connected, its events show up in the workflow editor's trigger picker, and the fields the event carries become variables every later step can read — so the message you send is written from what actually happened.
- A ticket is created
- A ticket changes status
- A comment is added to a ticket
The picker is the authority on which events your Zendesk connection publishes — these are the kinds that apps of this sort emit.
03 · THE AI AGENT STEP
One step that decides which Zendesk tools to call.
A workflow's AI Agent step runs a bounded tool-calling loop over the apps you have connected and returns an object whose fields you declared. So "find the record, check the status, and give me status and owner" is one step rather than four — and the fields it returns are available to every step after it.
You declare the output
The rows you name become the variables downstream steps read, so a branch can test what Zendesk said.
You cap the effort
A step budget and a model tier per node — the loop stops where you told it to.
Only what you switched on
The loop can call the Zendesk tools you left enabled and nothing else.
What teams do with it
Two ways Zendesk earns its connection.
02
Escalate without retyping
A workflow opens a Zendesk ticket from a conversation the AI agent could not resolve, carrying the transcript, the customer and the label that caused the escalation.
Setup
Connect Zendesk in about a minute.
- 1
Open Settings → Apps
It is open to everyone in your organization, not just admins — which apps your copilot can reach is part of doing the job.
- 2
Find Zendesk in Browse
The catalogue runs to hundreds of apps and is searchable. Connect Zendesk from its card.
- 3
Authorize with your own Zendesk account
You sign in on Zendesk's own screen and approve the access. The connection carries that account's permissions — no API keys are pasted into Cloodot.
- 4
Choose the tools it may call
Open the connection and switch off anything you would rather it never touched. A tool you switch off is out of reach from the next question onward.
Zendesk questions.
How do I connect Zendesk to Cloodot?
Open Settings → Apps in Cloodot, switch to Browse, and search for Zendesk. Connecting it opens Zendesk's own sign-in and consent screen; when you come back, the app is listed as Connected and your copilot can use it. Nothing is installed and no keys are pasted into Cloodot.
What can Cloodot do in Zendesk?
Work of this kind: search tickets by requester, status, tag or text; read a ticket and its full comment history; create a ticket from a conversation; add a public reply or an internal note to a ticket; change status, priority, assignee or tags; look up the requester and the organization behind a ticket. The exact list depends on what your Zendesk account is allowed to do — Settings → Apps shows every tool the connection actually exposes.
Can I limit which Zendesk tools Cloodot may use?
Yes. Open the connection and every tool it exposes is a switch, searchable by name. A tool you switch off is out of reach from the next question onward, so a read-only Zendesk connection is a matter of leaving the writes off.
Can an event in Zendesk start a Cloodot workflow?
Yes. Events like a ticket is created, a ticket changes status, a comment is added to a ticket appear in the workflow editor's trigger picker once Zendesk is connected, and the event's own fields become variables the rest of the workflow can read.
Who in my team can connect Zendesk?
Anyone in the organization — Apps is not restricted to admins and owners, because which apps a copilot can reach is part of doing the job. The connection carries the permissions of the Zendesk account that authorized it, so a support & ticketing connection is only ever as broad as the account behind it.
More support & ticketing
Rarely just one app.
IntercomA messaging-first support platform with conversations, contacts and articles in one place.GorgiasA helpdesk built for online stores, where a ticket usually has an order sitting behind it.
Zoho DeskZoho’s helpdesk, and the ticket queue for teams already running the rest of the Zoho suite.
HubSpotA CRM and marketing suite where most small and mid-sized teams keep the record of a customer.
SalesforceThe enterprise CRM of record, and usually the system every other tool is reconciled against.Zoho CRMZoho's CRM — often the system of record for teams already running the wider Zoho suite.See it on your own inbox
Try the whole thing, today.
Start free. Connect a channel, train an agent on your own content, and you'll have a working deployment in your inbox the same afternoon.