Resources · Zapier integration

Zoho Desk Zapier integrationAutomate Zoho Desk with Zapier.

The Zoho Desk Zapier integration gives you 10 triggers, 9 actions and 3 searches to plug your help desk into the rest of your tools. All 10 triggers are instant and the app runs on the free plan. Here is what each one does, what it costs, and where it catches people out.

See the 22 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Zoho Desk Zapier integration actually gets you

Hooking Zoho Desk up to Zapier means the day-to-day of your support queue (a new ticket, a reply, a status change, a new contact) can set off a chain of steps without an agent lifting a finger. It also runs the other way: Zapier can open tickets, send email replies, add comments and update contacts in Zoho Desk from what other tools send it.

Three outcomes cover most of the value. Context on every new ticket: New Ticket starts the Zap and Add Comment drops a private note with whatever the agent needs before replying. Requests from everywhere, in one queue: Create Ticket turns a form entry, a chat transcript or a failed order from another tool into a ticket in the right department. No duplicate customers: Find Contact, in its find-or-create form, matches people by email before anything new gets created.

What Zapier does not do here: there's no action to delete a ticket, close an account or publish a knowledge base article. Articles and agents only flow out of Zoho Desk, through their triggers. Anything else goes through API Request (Beta), which assumes you can read Zoho's API docs.

Weighing your options? The same app is covered on Make: Zoho Desk Make integration. And if you'd rather have someone build it for you, there's our Zapier agency.

Vocabulary

Zapier jargon, decoded

Eight words, and the rest of this page reads easily.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for that event.
Action
What the Zap does once it starts: the step that writes, sends or creates something in an app on your behalf.
Task
What Zapier bills you for: one action completed successfully. Your plan allowance is a count of tasks, not of Zaps.
Instant trigger
The app itself pings Zapier the moment the event happens, so nothing waits for a scheduled check. All Zoho Desk triggers work this way.
Polling trigger
Zapier asks the app for new items on a fixed timer, then keeps only the ones it hasn't seen before.
Filter
A step that only lets the Zap carry on when the incoming data meets your condition, and stops it otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can use what it found.
Cost

What it really costs you

Zoho Desk isn't a premium app, so it works on Zapier's free plan. What you actually need to watch is your task count.

  • Premium appNo, available on the free plan
  • Free plan tasks100 per month
  • Free plan Zap sizeTwo steps: one trigger, one action
  • Zoho Desk triggers10 instant, 0 polling

Your Zap's trigger never costs a task, and Zapier doesn't charge for watching for new tickets. Every successful action counts as one task, so a three-action Zap burns three times what a one-action Zap does. Failed actions don't count. The free plan gives you 100 tasks a month but only two-step Zaps, so adding a filter or a search makes the Zap multi-step and pushes you onto a paid plan. Since all 10 Zoho Desk triggers are instant, the polling grid below doesn't apply to them.

Connect

Connect your Zoho Desk account

  1. 01

    Start from the Apps page

    In your Zapier account, open the Apps page and click + Add connection. A connection is your Zoho Desk account linked to Zapier once, then reused by every step that needs it.

  2. 02

    Pick Zoho Desk

    Search for "Zoho Desk" in the dialog, select it and confirm with Add connection. You need a working Zoho Desk account, with read or write access to anything the Zap should touch.

  3. 03

    Sign in and grant access

    Log in to Zoho Desk in the tab that opens, then grant Zapier access to the account. Without that, no step will be able to read a ticket or write to one.

First Zap

Build your first Zap: a private note on every new ticket

GoalAdd an internal comment to selected new Zoho Desk tickets the moment they're created, so agents start with context.

  1. 01

    Set the trigger

    In the Build stage, choose Zoho Desk and the New Ticket event. Fill in the organization and the department to watch; both are required.

  2. 02

    Test it on a real ticket

    Test the trigger. Zapier brings back the three most recent tickets in that department. Pick one that looks like a genuine request: that's what you'll map against.

  3. 03

    Add a filter

    Use the plus icon to add Filter, then set the field to check, the rule and the value. Mind the rule type: a text rule only works on text.

  4. 04

    Add the comment

    Add Zoho Desk with Add Comment. Use the same department, map the ticket from the trigger, write the content, and set Public to keep it internal.

  5. 05

    Test and publish

    In the Test stage, run each step once and check the note in Zoho Desk. If it looks right, hit Publish to switch the Zap on.

Triggers

All 10 Zoho Desk triggers

10 events start a Zap when something happens in Zoho Desk, and 10 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Account

Instant trigger

In Zapier“Triggers when a new account is created.”

Fires when an account (the customer company your contacts belong to) is created in Zoho Desk, and hands its record to the Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a B2B software vendor that wants the account manager pinged whenever a new company shows up in support.
Watch out
if this same Zap creates accounts with Create Account, it fires itself again.
2

New Agent

Instant trigger

In Zapier“Triggers when a new agent is added.”

Every agent added to your Zoho Desk kicks off the Zap. It's your signal that someone new just joined the support team.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a support lead who wants an onboarding checklist created in the team's project tool for each new hire.
Watch out
Zapier has no action to add agents to Zoho Desk. You add them in the app; the Zap only follows along.
3

New Article

Instant trigger

In Zapier“Triggers when a new article is published.”

Starts the Zap when an article is published in your Zoho Desk knowledge base, so new help content doesn't go unnoticed.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a customer education team that wants each new help article shared with customer success managers.
Watch out
it's one-way. Zapier has no action to write or edit an article.
4

New Attachment

Instant trigger

In Zapier“Triggers when a new attachment is added to any ticket in the selected organization.”

Any file added to any ticket in the selected organization is enough to start the Zap, whether it's a screenshot, a receipt or a log file.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a hardware startup that wants every bug screenshot customers send copied to its engineering storage.
Watch out
it covers the whole organization. Pair it with Add Attachment and it loops.
5

New Comment

Instant trigger

In Zapier“Triggers when a new comment is added to any ticket in the selected department.”

A comment on any ticket in the chosen department wakes the Zap up. Useful for getting agents' internal notes out of Zoho Desk.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a tier-one team that wants engineers alerted whenever a comment asks for their input.
Watch out
the department is required, and comments elsewhere don't reach the Zap. End this same Zap on Add Comment and it can set itself off.
6

New Contact

Instant trigger

In Zapier“Triggers when new contact is created.”

A new person saved in Zoho Desk launches the Zap with their record. In support, that's often the first sign of a new customer.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a meal-kit brand that wants every customer who writes in added to a feedback list in its email tool.
Watch out
if this same Zap creates contacts, with Create Contact or the find-or-create version of Find Contact, it can set itself off again.
7

New Message

Instant trigger

In Zapier“Triggers when a new message is added to any ticket in the selected department.”

Each message added to a ticket in the chosen department sets the Zap off. It's the heartbeat of the conversation between customer and agent.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an IT managed-services firm that mirrors each ticket message into the client's shared channel.
Watch out
organization and department are both required. A ticket filed in another department won't reach this Zap.
8

New Status Change

Instant trigger

In Zapier“Triggers when a status of ticket is changed.”

Runs when a ticket changes status. The status to watch is a required field you set in the trigger.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a SaaS company that sends a satisfaction survey from its survey tool when a ticket is marked solved.
Watch out
organization, department and status are all required, so decide which status matters before you build.
9

New Ticket

Instant trigger

In Zapier“Triggers when a new ticket is created.”

A freshly created ticket in the chosen department starts the Zap. It's the bread-and-butter trigger of any automated help desk.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a hosting provider that wants the on-call engineer paged as soon as a ticket lands in the outages department.
Watch out
if the Zap creates tickets in that same department with Create Ticket, it loops.
10

Updated Ticket

Instant trigger

In Zapier“Triggers when a ticket is updated.”

Any change to a ticket in the chosen department fires the Zap again. Broader than a status change, it reacts to every edit.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
an agency that keeps a client-facing tracker in sync with the state of each support ticket.
Watch out
pair it with Update Ticket and you've built the perfect loop. Your task count melts fast.
Actions

All 9 Zoho Desk actions

Zoho Desk gives you 9 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Attachment

Action

In Zapier“Add an attachment to a ticket.”

Attaches a file to an existing ticket using its ticket ID. By default the attachment stays private.

When to use it
attach the return label generated by your shipping tool to the matching ticket.
Watch out
it asks for the ticket ID. Get it from a trigger or from Search Ticket.
2

Add Comment

Action

In Zapier“Add a comment to a ticket.”

Adds a comment to a ticket. You decide whether it's public, so the customer sees it, or kept for the team.

When to use it
paste a customer's plan and billing status from another tool onto the ticket as a private note.
Watch out
the Public setting is required. Double-check it before you publish.
3

Create Account

Action

In Zapier“Creates a new account.”

Creates an account, meaning the customer company, in Zoho Desk. The account name is enough, along with the organization.

When to use it
a company that signs in your CRM should be set up in support before its staff start writing in.
Watch out
run Find Account first so the same company isn't created twice.
4

Create Contact

Action

In Zapier“Creates a new contact.”

Saves a new person in Zoho Desk. Only the last name is required, plus the organization.

When to use it
a first-time buyer from your store should already exist in support before their first question.
Watch out
to avoid creating someone twice, use the find-or-create version of Find Contact, which looks people up by email first.
5

Create Ticket

Action

In Zapier“Creates a new ticket for customer requests.”

Opens a ticket in Zoho Desk from a request that came in somewhere else. It needs a department, a contact and a subject.

When to use it
every bug report submitted through your in-app widget should become a tracked ticket.
Watch out
the contact is required. Put Find Contact first if the person might not exist yet.
6

Send E-Mail Reply

Action

In Zapier“Sends an email reply for the selected ticket.”

Sends an email reply on a given ticket, from the address you choose. A setting also lets it forward instead of reply.

When to use it
acknowledge an out-of-hours request with a prepared message so nobody waits in silence.
Watch out
from address, to address, content type and reply content are all required. Miss one and the step fails.
7

Update Contact

Action

In Zapier“Updates an existing contact.”

Edits an existing contact in Zoho Desk. You point to the contact, then set what changes.

When to use it
push a phone number a customer just updated in their account page through to support.
Watch out
without the right contact, nothing moves. Find Contact upstream finds them by email.
8

Update Ticket

Action

In Zapier“Updates an existing ticket.”

Changes a ticket that already exists in the chosen department. It's the action that moves tickets along without an agent stepping in.

When to use it
raise a ticket's priority when the customer's account is flagged as at risk in your CRM.
Watch out
never in a Zap that starts on Updated Ticket for the same tickets, or the Zap fires itself again and again.
9

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

An advanced action that sends a raw request to Zoho Desk using your existing connection. The escape hatch when nothing ready-made fits.

When to use it
a job none of the ready-made actions covers, once you know which Zoho Desk API call does it.
Watch out
you need to know the Zoho Desk API, and the URL must sit on a domain tied to the app.
Searches

All 3 Zoho Desk searches

3 search steps look for data that already exists in Zoho Desk, so a later step can use it.

Searches sit at the bottom of the Action event list, under the SEARCH heading. They fetch a ticket, an account or a contact that already exists and pass it to the steps that follow. Three settings decide what happens when the result isn't what you expected.

1

Search Ticket

Search

In Zapier“Search Ticket (Request) by Ticket number.”

Finds a ticket by its number inside the chosen department, so later steps can use everything on it.

When to use it
a customer quotes their ticket number on another channel and you want the follow-up attached to the right case.
Watch out
organization, department and ticket number are all required. A ticket in another department stays invisible.
2

Find Account

Search

In Zapier“Finds an account from the system.”

Looks up an existing account in Zoho Desk so the rest of the Zap works on the right customer company.

When to use it
before Create Account, to check the company isn't already on file.
Watch out
the only required field is the organization. Set the no-result behavior with care.
3

Find Contact

SearchFind or create

In Zapier“Finds an existing contact by email.”

Finds an existing contact by email address. The editor also lists Find or Create Contact: that isn't an extra operation, just this search with the create box ticked.

When to use it
right before Create Ticket, to attach the request to the right person or create them if missing.
Watch out
the email is required. Without it there's nothing to search on.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap and skips the steps that relied on it. Turned on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking this turns the search into a find-or-create. The setting above disappears and the step asks for the fields needed to create the item.
  3. If multiple search results are found?
    Three ways out: keep the first match (the default), stop the Zap, or pass every match along at once.
When it breaks

When it breaks

Zapier doesn't link any help article specific to Zoho Desk. So the failures to plan for are the ones every Zap can hit, with a help-desk flavor.

These four show up as soon as tickets start moving. If a Zap stalls and you can't see why, the Zapier troubleshooting page is the next stop.

  • Old tickets never come through

    A Zap only reacts to what happens after you switch it on. Tickets already open in Zoho Desk are left alone; moving that backlog is a separate job.

  • The Zap that triggers itself

    Update a ticket in a Zap that starts on Updated Ticket, or comment from New Comment, and it fires itself over and over, draining your tasks.

  • A bulk import gets held back

    After a contact import or a migration into Zoho Desk, a sudden flood of new records can be held back by Zapier's flood protection.

  • The wrong department

    Five triggers and several actions require a department. A ticket filed elsewhere is neither seen by the Zap nor found by Search Ticket.
Need help

Need help automating Zoho Desk with Zapier?

A person reads every message.

FAQ

Frequently asked questions

01Is the Zoho Desk Zapier integration free?
Yes, within the limits of Zapier's free plan. Zoho Desk isn't a premium app, so it works there. The free plan gives you 100 tasks a month and as many Zaps as you like, but each one is capped at two steps: one trigger and one action. Add a filter, a search such as Find Contact, or a second action, and the Zap becomes multi-step and needs a paid plan. A simple setup like adding a note to every new ticket fits on the free plan.
02How many tasks does a Zoho Desk Zap use?
One task per successful action, nothing else. The trigger, whether it's New Ticket or New Status Change, never costs a task, and an action that fails isn't counted. A Zap that chains three actions uses three tasks every run. The real danger on a help desk is looping: a Zap that updates tickets while starting on Updated Ticket keeps firing itself and can burn through the 100 monthly tasks of the free plan in no time.
03Do Zoho Desk triggers fire in real time?
Yes, all ten. Zoho Desk tells Zapier as soon as a ticket, message, comment, contact or any other tracked item appears, and the Zap starts right away. The polling grid, from 15 minutes on Free down to one minute on Team and Enterprise, only applies to polling triggers, and Zoho Desk has none. So even a free account reacts without waiting. In the editor, a Zap built on an instant trigger shows a small lightning bolt.
04What do you need to connect Zoho Desk to Zapier?
An active Zoho Desk account, plus access to whatever the Zap will read or write. You connect from the Apps page in Zapier with + Add connection: search for Zoho Desk, confirm, sign in in the tab that opens and grant access. What usually blocks people is the Organization and Department fields, required on most ticket operations. The connected account needs access to the department you're targeting, since that's the one you pick there.
05Why does a Zoho Desk Zap keep looping?
Because it writes to the very place its own trigger is watching. Zoho Desk has plenty of risky pairs: Updated Ticket with Update Ticket, New Comment with Add Comment, New Attachment with Add Attachment, New Contact with Create Contact or the find-or-create version of Find Contact. Each run sets off the next, and each successful action costs a task. The fix is to keep the action from writing where the trigger watches: another department, or a trigger that doesn't react to what the action produces.
06What if the operation you need doesn't exist?
Use API Request (Beta). It sends a request straight to the Zoho Desk API through your existing connection, so you don't handle authentication yourself. It's the route for anything the ready-made actions don't cover, such as deleting a ticket or editing a knowledge base article, provided the Zoho Desk API offers it. The catch is that you need to read the API documentation, choose the right HTTP method and use a URL on one of the app's domains. The Stop on error setting decides whether the Zap halts when Zoho Desk returns an error.
07Zapier, Make or n8n for Zoho Desk?
It comes down to criteria, not a ranking. First, check that the tool offers the exact operations you need: on Zapier, Zoho Desk has 22 operations, with ticket and contact updates but no deletes outside API Request. Next, look at how usage is counted: Zapier bills each successful action, and its free plan stops at two-step Zaps. Finally, think about who will maintain the automation and whether your support team needs to be able to read it. Score each tool on those points.
Same platform

Other docs you might need on this stack.

Browse all integrations