> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/dokumentation/automation/connectors/zoho-desk.md).

# Zoho Desk

Zoho Desk connector: create and maintain tickets, comments, attachments and contacts in Zoho Desk from flows – connection, actions, examples.

**Path:** "Automation" → "Workflows" → flow designer → **"Zoho Desk"** module

The **Zoho Desk connector** connects equipme in [workflows](https://hub.equipme.io/dokumentation/automation/workflows.md) with your Zoho Desk helpdesk. Events in equipme create tickets, or information from equipme is added to the right ticket as a comment or attachment.

## What for?

* **Onboarding:** new employee in equipme → ticket for IT in Zoho Desk ("Set up workstation").
* **Offboarding:** employee moves to status "offboarding" → ticket for returns and account lock, with the list of assigned assets as a comment.
* **Orders:** approved order request → ticket for provisioning the device.
* **Documents on the ticket:** generate a handover protocol as a PDF and attach it to the ticket.
* **Maintain contacts:** create new employees as contacts in Zoho Desk so they can open tickets themselves.

## Prerequisites

* The activated [Automation module](https://hub.equipme.io/dokumentation/automation.md)
* A Zoho Desk account in Zoho's **EU data center** (sign-in via zoho.eu)
* A Zoho Desk user with permission to read, create and update tickets and contacts and to read departments, teams, agents and products
* For examples using equipme data, a connection of the [equipme connector](https://hub.equipme.io/dokumentation/automation/connectors/equipme.md)

## Setting up the connection

1. In the flow designer, drag a component of the "Zoho Desk" module onto the canvas (e.g. *AddTicket*).
2. Click **Connect account**.
3. Sign in with the Zoho Desk user in the Zoho sign-in window and confirm access.
4. The connection appears under **"Accounts"** with the name of the Zoho profile and is available to all components of the module.

{% hint style="info" %}
The connection works with the permissions of the signed-in Zoho user. Ideally use a dedicated user for automation so that tickets and comments are clearly recognizable as automatically created.
{% endhint %}

## Basic terms

* **Organization ID:** Zoho Desk can hold several organizations (portals) under one account. Every action first asks which organization it works in. The selection list shows the organizations of the connected account.
* **Dependent selection lists:** department, team, contact, product and agent are loaded from Zoho Desk once the organization is selected. Instead of picking from the list, you can also insert an ID from a previous component.
* **IDs:** you pass ticket and comment IDs from previous steps (e.g. from the result of *AddTicket* or *ListTickets*).

## Triggers

The connector has **no triggers of its own**. Flows start via other triggers – e.g. a trigger of the [equipme connector](https://hub.equipme.io/dokumentation/automation/connectors/equipme.md) (*New Employee*, *New Order Request*), a schedule (Scheduler) or a webhook from Zoho Desk.

## Actions

### Tickets

| Component    | Purpose                              | Key options                                                                                                                                                                                                                                                                                                                      |
| ------------ | ------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| AddTicket    | Create a new ticket                  | Required: Organization ID, Subject, Department ID, Contact ID. Optional: Description, Status, Priority, Assignee ID, Team ID, Product ID, Category, Subcategory, Classification ("Problem", "Request", "Question", "Others"), Due date, Channel, Language, Email, Phone, Shared departments, Secondary contacts, Customer fields |
| UpdateTicket | Change an existing ticket            | Required: Organization ID, Ticket ID. All fields of *AddTicket* plus Resolution; only filled-in fields are changed                                                                                                                                                                                                               |
| GetTicket    | Read a ticket with all fields        | Organization ID, Ticket ID                                                                                                                                                                                                                                                                                                       |
| ListTickets  | Read all tickets of the organization | Organization ID; returns the complete list without filters                                                                                                                                                                                                                                                                       |

### Comments and attachments

| Component           | Purpose                            | Key options                                                                                                                                                                                                   |
| ------------------- | ---------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| AddTicketComment    | Write a comment on a ticket        | Ticket ID, Content, Content type ("HTML" or "PlainText", default HTML), Is public (visible to the contact or internal only), Attachments (dynamic) from previous steps or Attachments (static) as fixed files |
| UpdateTicketComment | Change an existing comment         | Ticket ID, Comment ID, Content, Content type, Attachments                                                                                                                                                     |
| AddTicketAttachment | Attach a file directly to a ticket | Ticket ID, Attachment (file, e.g. from *HtmlToPdf*), Is public                                                                                                                                                |

### Contacts and teams

| Component  | Purpose                       | Key options                                                                                                                                                                                                     |
| ---------- | ----------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| AddContact | Create a new contact          | Required: Organization ID, Last name. Optional: First name, Email, Secondary email, Phone, Mobile, Title, Type, Account ID, address (Street, Zip, City, State, Country), Language, Description, Customer fields |
| ListTeams  | Read the organization's teams | Organization ID                                                                                                                                                                                                 |

## Examples

### Onboarding ticket for IT

1. **Equipme › New Employee** – trigger, filtered to the relevant locations.
2. **Zoho Desk › AddTicket** – Subject "Onboarding: {first name} {last name}", Department ID = IT, Contact ID = IT coordination, Due date = start date, Classification "Request", Description with location, cost center and supervisor.
3. **Equipme › Update Employee Metadata** – store the Zoho Desk ticket ID on the employee so later comments go to the same ticket.

### Offboarding with asset list

1. **Equipme › List Employees** – daily via schedule, filtered to employees with status "offboarding", Output Type "One item at a time".
2. **Equipme › List Service Instances** – read the employee's assets.
3. **Zoho Desk › AddTicket** – create the ticket "Offboarding: returns".
4. **Zoho Desk › AddTicketComment** – asset list as an HTML table, Is public off (internal comment).

### Attach a handover protocol

1. **Equipme › New Fulfillment Order** – trigger on a new delivery.
2. **PDF › HtmlToPdf** – generate a handover protocol with device, serial number and employee (see [Utility modules: Lists and PDF](https://hub.equipme.io/dokumentation/automation/connectors/utilities.md)).
3. **Zoho Desk › AddTicketAttachment** – attach the file from step 2 to the related ticket.

## Notes and limits

* The connector only supports Zoho accounts in the **EU data center**.
* *ListTickets* reads **all** tickets of the organization – for large helpdesks this takes time and causes many requests. For single tickets use *GetTicket* and store the ticket ID, e.g. as metadata in equipme.
* Status, priority and category are free-text fields. The values must match exactly the values configured in Zoho Desk.
* Zoho Desk expects custom fields ("Customer fields") in JSON format with the API names of the fields.
* All actions work with the permissions of the connected Zoho user.

## Troubleshooting

| Problem                                         | Cause / solution                                                                                                                          |
| ----------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| Sign-in at "Connect account" fails              | The account is not in the EU data center, or the user has no access to Zoho Desk.                                                         |
| Selection list (e.g. Department ID) stays empty | Select the Organization ID first. If the list stays empty, enter the ID from Zoho Desk directly or take it from a previous step.          |
| "Unauthorized" or "Forbidden" error             | The Zoho user lacks permission for this department or action, or the connection was revoked. Test under "Accounts" or reconnect.          |
| Ticket is not created                           | Check required fields: Subject, Department ID and Contact ID. Status and priority values must exist in Zoho Desk.                         |
| Attachment missing                              | With "Attachments (dynamic)" the file must come from a previous step. With *AddTicketAttachment*, map the file in the "Attachment" field. |

Logs of every run are available under **"Insights"**.

## Frequently asked questions

**Can a new ticket in Zoho Desk start a flow?**

Not via a component of this connector. Set up a webhook in Zoho Desk that calls a webhook trigger in the flow designer, or poll tickets on a schedule with *ListTickets*.

**Do employees see automatically created comments?**

Only if "Is public" is enabled. Create internal notes (e.g. asset lists) with "Is public" disabled.

**How do I find the matching ticket for an employee later?**

After *AddTicket*, store the ticket ID as metadata on the employee (*Update Employee Metadata*) and read it back in later flows.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hub.equipme.io/dokumentation/automation/connectors/zoho-desk.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
