ActionZoho DeskUpdated September 2026

How do I list Zoho Desk tickets?

Short answer: You can list tickets in Zoho Desk by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Zoho Desk List Tickets action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Tickets in Zoho Desk — start free All 5 Zoho Desk actions

List Tickets in Zoho Desk — start free

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Organization ID orgId	string	Required	Organization ID. Example: 12345678
Status Filter status	string	Optional	Status Filter. Example: Open
Department ID departmentId	string	Optional	Department ID
Limit (max 50) limit	string	Optional	Limit (max 50). e.g. "50"
Sort By sortBy	options	Optional	Sort By. Options: Created Time, Due Date, Recent Thread

Sample request

{
  "orgId": "e.g. 12345678",
  "status": "e.g. Open",
  "departmentId": "{{trigger.departmentId}}",
  "limit": "50",
  "sortBy": "{{trigger.sortBy}}"
}

Returns

{
  "data": [
    {
      "id": "46000000009001",
      "status": "Open",
      "subject": "Help",
      "priority": "Medium",
      "ticketNumber": 101
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for List Tickets.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Zoho Desk

2 Google Sheets triggers

HubSpot → Zoho Desk

18 HubSpot triggers

FAQ

Questions about List Tickets.

What does the List Tickets action do in Zoho Desk?

Lists tickets from Zoho Desk with filters for status, assignee, department, and contact. Used for SLA reports, queue dashboards, or warehouse exports.

What inputs does List Tickets require?

Required: Organization ID. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Zoho Desk returns an error?

The run history shows the failed step with its input and the error message Zoho Desk returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does List Tickets support batch operations?

Run List Tickets inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Zoho Desk's rate limits.

More actions