Resources · Make integration

Zoho Desk Make integrationAutomate Zoho Desk with Make.

Tired of copying requests into Zoho Desk by hand? The Zoho Desk Make integration gives you 10 modules: 8 actions and 2 searches that create, update, comment on and close tickets for you. This guide connects your account, builds a first scenario with you and explains each module in plain words.

Try the Zoho Desk integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Zoho Desk Make integration do for you?

The Zoho Desk Make integration links your help desk account to Make so that tickets, contacts, accounts and tasks change on their own when something happens elsewhere. You build a scenario, the automation itself, by chaining modules: each module is one brick, like creating a ticket or searching contacts. No code involved.

Turn outside requests into tickets. A form, an email or a chat message arrives in another app, and Create an Object opens the matching ticket in Zoho Desk. Add a Comment can then attach the context your agents need before they read it.

Keep customer records in step. When a customer changes their details in your CRM, Search Objects finds the contact in Zoho Desk and Update an Object writes the new values, so agents never answer with stale data.

Clean the queue in bulk. List Objects pulls a set of tickets, then Close Tickets or Edit Spam Objects handles them in one move instead of one click per ticket.

Know the limit before you start: Zoho Desk has no trigger module in Make, so a scenario cannot wake up by itself when a ticket appears in Zoho Desk. It starts from another app or from a schedule. Anything the 10 modules skip goes through Make an API Call. If you are still choosing a tool, read our Make review and the n8n vs Make comparison; if you would rather learn to build it yourself, start with our Make training.

Connect

How do you connect Zoho Desk to Make?

  1. 01

    Copy your organization ID

    In Zoho Desk, click the Setup icon in the top-right corner, then open API under Developer Space. In the Zoho Service Communication (ZSC) Key section, copy the OrgId value.

  2. 02

    Create the connection in Make

    Add any Zoho Desk module to your scenario and click Create a connection. A connection is your Zoho Desk account linked to Make once, then reused by every Zoho Desk module. Paste the ID into the Organization ID field.

  3. 03

    Save and approve access

    Give the connection a clear name if you like, click Save, then sign in to Zoho Desk and confirm access when the window asks for it. The module can now read the objects of your account.

First scenario

Your first scenario: turn a request into a Zoho Desk ticket

GoalWhen a customer request lands in another app, Make opens a ticket in Zoho Desk and adds a comment with the context.

  1. 01

    Start a new scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where requests arrive, such as your form or inbox tool, and choose its module that watches new entries.

  2. 02

    Add Create an Object

    Click the + on the right, search for Zoho Desk and pick Create an Object. Click Create a connection if you have not linked your account yet, then choose tickets as the object type.

  3. 03

    Map the request

    Fill the ticket fields with data from the first module: the sender, the subject, the message. Make lists what your account can read once the connection exists, so there is nothing to type from memory.

  4. 04

    Attach a comment

    Add Add a Comment after it and map the ticket ID returned by the previous module. Write the note your agents should see first, for example where the request came from.

  5. 05

    Test, then switch it on

    Click Run once and read the bundle each module received; a bundle is one item passed along, here one request. Set the schedule on the first module, every 15 minutes by default, and turn the scenario on.

Modules

What each Zoho Desk module does

Zoho Desk gives you 10 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Actions

8 modules
Zoho Desk1

Get an Object

Action

In Make“Returns only one object that has a specified id from a selected module (ex: a task, a ticket, an account ...).”

Fetches one ticket, account, task or other record from Zoho Desk when you already know its ID, so the next modules can use its full details.

When to use it
an earlier step handed you a ticket ID and you need the rest of the ticket before replying or updating it.
Watch out
without a valid ID it has nothing to return; if you only know a name or an email, start with Search Objects.
Zoho Desk2

Create an Object

Action

In Make“Creates an object based on a selected module (ex: create an account, create a contact, create a ticket ...).”

Adds a new record to the Zoho Desk module you choose, whether that is a ticket, a contact or an account, filled with data mapped from earlier steps.

When to use it
a request arrives through a form, a shop order or a chat tool and it deserves its own ticket without anyone retyping it.
Watch out
each run creates a fresh record, so check first with Search Objects if the contact may already exist.
Zoho Desk3

Delete an Object

Action

In Make“Deletes a specified object based on id from a selected module (ex: delete an account, delete a contact, delete a ticket ...).”

Removes a record, such as a test ticket or a duplicate contact, from the selected Zoho Desk module, identified by its ID.

When to use it
cleaning out records your scenario spotted as duplicates or created by mistake while testing.
Watch out
it deletes whatever ID it receives, so run Run once on a record you can afford to lose before switching the scenario on.
Zoho Desk4

Update an Object

Action

In Make“Updates a specific object based on id from a selected data (ex: update an account, update a ticket, update a contact ...).”

Changes the values of an existing ticket, contact or account, found by its ID, so Zoho Desk reflects what changed in your other tools.

When to use it
a customer updates their phone number in your CRM and the matching Zoho Desk contact should follow without anyone copying it.
Watch out
the module needs the record ID; pair it with Search Objects when you only know the email.
Zoho Desk5

Add a Comment

Action

In Make“Adds a comment to an object based on id for a particular module (tasks, tickets).”

Posts a comment on a ticket or a task, which gives agents the background they need right inside the record they are working on.

When to use it
right after a ticket is created, to log where the request came from or what an outside tool found about the customer.
Watch out
it only works on tickets and tasks, not on contacts or accounts.
Zoho Desk6

Close Tickets

Action

In Make“Closes one or more tickets by specifying the ticket ID(s) in a list.”

Closes one ticket or a whole batch at once from a list of IDs, which spares your agents a long round of clicks in the queue.

When to use it
an order is marked delivered in your shop and every open ticket about it can be resolved together.
Watch out
the IDs must arrive as a list; collect them with List Objects or Search Objects first.
Zoho Desk7

Edit Spam Objects

Action

In Make“Sets or unsets contacts/tickets as spam by specifying their ids into a list.”

Marks contacts or tickets as spam, or clears that flag, for every ID you pass in a list, so junk stops cluttering the queue.

When to use it
a filter in another tool has flagged a sender as junk and you want Zoho Desk to treat their tickets the same way.
Watch out
the same module both sets and removes the flag, so double-check which one you chose before activating.
Zoho Desk8

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the Zoho Desk API to your scenario, using the connection you already have, for anything the ready-made modules leave out.

When to use it
you need an endpoint listed in the Zoho Desk API documentation that none of the other nine modules covers.
Watch out
you describe the request yourself here, so keep the Zoho Desk API documentation open while you set it up.

Searches

2 modules
Zoho Desk9

Search Objects

Search

In Make“Returns multiple objects based on a search criteria from a selected module(ex: accounts where account name contains 'Joe', tickets where subject contains 'Hello', contacts where email contains domain '@gmail.com' ...).”

Finds the records that match a criterion, for instance tickets whose subject contains a word or contacts from a given email domain, and passes each one on.

When to use it
you know an email or a subject line but not the ID that Update an Object or Close Tickets needs.
Watch out
it can return zero, one or several bundles, and each one triggers the next modules, which counts operations on your plan.
Zoho Desk10

List Objects

Search

In Make“Returns a list that contains multiple objects from a selected module (multiple accounts, multiple contacts, multiple tickets ...).”

Pulls a series of records from one Zoho Desk module, such as all tickets or all contacts, without any search condition.

When to use it
exporting accounts to a spreadsheet or feeding a batch of tickets into Close Tickets.
Watch out
every record becomes a bundle and every later module runs once per bundle, so an operation, one module run, adds up quickly; prefer Search Objects when you can narrow the list.
Need help

Need help automating Zoho Desk with Make?

A person reads every message.

FAQ

Zoho Desk and Make: frequent questions

01Is the Zoho Desk Make integration free?
Yes, Zoho Desk is a standard app in Make, so its 10 modules work on the Free plan. The Free plan limits you to 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in operations per month. Your Zoho Desk subscription is a separate matter that this page does not cover.
02What do you need to connect Zoho Desk to Make?
A Zoho Desk account and your organization ID. You find the ID in Zoho Desk under Setup, Developer Space, API, in the Zoho Service Communication (ZSC) Key section, where it appears as OrgId. In Make, click Create a connection on any Zoho Desk module, paste it into the Organization ID field, save and approve access. The documentation lists no other prerequisite. Companies with their own Zoho app can add its client credentials under Advanced settings.
03Can a new Zoho Desk ticket start a Make scenario on its own?
No, Zoho Desk offers no trigger module in Make, neither scheduled nor instant. A scenario therefore starts in one of two ways. Either another app triggers it, such as a form or an inbox receiving a request, or you set a schedule on the first module, every 15 minutes by default, and let a module like Search Objects or List Objects fetch the tickets to handle. On the Free plan, 15 minutes is the shortest interval; paid plans go down to 1 minute.
04What if the Zoho Desk module you need is missing in Make?
Use Make an API Call. It sends any request the Zoho Desk API accepts, with the connection you already set up, so you are not limited to the 10 ready-made modules. Check the Zoho Desk API documentation for the endpoint and its parameters. The Make documentation gives no numeric limit for this app, so the constraints you will meet are those of your Make plan, such as the 5 MB file size or the execution time on the Free plan.
05Should you use Make or n8n for Zoho Desk?
It depends on the tool you already run and the way you like to build. On Make, Zoho Desk gives you 8 actions and 2 searches, starts on the Free plan and covers the rest of the API through Make an API Call; it has no trigger, so scenarios start from another app or a schedule. n8n often offers a node for the same app, so compare the two on the actions you need rather than on reputation. Our n8n vs Make comparison sets out the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations