Short answer: Drop the "Zoho Desk → List Tickets" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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 |
{"orgId": "e.g. 12345678","status": "e.g. Open","departmentId": "{{trigger.departmentId}}","limit": "50","sortBy": "{{trigger.sortBy}}"}
{"data": [{"id": "46000000009001","status": "Open","subject": "Help","priority": "Medium","ticketNumber": 101}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.