Zoho Desk gives agents two built-in automation tools: macros, a one-click bundle of actions an agent runs manually on a ticket, and workflow rules, criteria-based rules that fire on their own when a ticket meets certain conditions. Both are genuinely useful and both are scoped to what Zoho Desk (and the Zoho apps connected to it) can see, which means anything the rule needs to do in an outside system has to be built separately.
A macro is the manual version: an agent clicks it on an open ticket and it runs a set of steps at once, updating the status, assigning the ticket, sending a canned reply, maybe adding a tag, instead of doing each one by hand. It's a shortcut, triggered by a person, every time.
A workflow rule is the automatic version: define the condition (a ticket comes in from a specific department, a priority field gets set to urgent, a ticket sits untouched past a time limit) and Zoho Desk runs the matching actions on its own, no agent involved. Time-based escalation rules in particular are how most teams handle SLA breaches without someone watching the clock manually.
Both tools operate entirely on data and actions inside Zoho Desk, plus whatever a connected Zoho app can natively reach. A workflow rule can update a field, send an email, or notify a Slack channel through the marketplace extension. It cannot check an inventory count in a warehouse system, create a bill in accounting software that isn't Zoho Books, or update a record in a CRM Zoho doesn't already talk to.
That's the point where it's no longer a Zoho Desk setting to turn on. It becomes an integration: something listening for the same trigger, reaching into the outside system through its API (or through browser automation if that system doesn't offer one for the piece you need), and acting there too.
A rule that only escalates or auto-assigns once it's confirmed something in an outside system, like an account's billing status or a shipment's current state, something the native rule builder has no way to check on its own.
A macro an agent already runs that, behind the scenes, also updates the order system, logs the resolution in accounting, and notifies the right internal channel, instead of three separate manual steps after the ticket closes.
If a macro or workflow rule needs to act on a system outside Zoho, tell us which one.
Tell us what the automation needs to check or update outside Zoho Desk. We'll scope what it takes to build that into the trigger directly, and the same gap shows up in plenty of other ticketing and helpdesk tools too, not just this one.
Let's talk →A macro runs when an agent clicks it, on one ticket at a time. A workflow rule runs on its own whenever a ticket matches the condition you set, with no agent involved. Macros are a shortcut for a person; workflow rules are the automatic layer.
Not natively, beyond what a marketplace extension already supports, like a Slack notification. Anything more specific, writing to an outside database or updating a record in a non-Zoho system, needs a custom integration built against the API.
Mostly SLA enforcement: escalating or reassigning a ticket automatically once it's sat untouched past a set amount of time, which is how most teams catch a slipping SLA without someone checking manually.
Zoho Desk's free tier is aimed at very small teams and trims back advanced features, so the deeper workflow automation generally sits on paid plans. Check Zoho's current pricing page for the exact split, since it shifts as Zoho updates its tiers.