Short answer: Drop the "Zoho Desk → Update Ticket" 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 |
Ticket ID ticketId | string | Required | Ticket ID. Example: 46000000009001 |
Subject subject | string | Optional | Message subject line. |
Status status | options | Optional | Status. Options: Open, On Hold, Escalated, Closed |
Priority priority | options | Optional | Priority. Options: Low, Medium, High, Urgent |
Assignee ID assigneeId | string | Optional | Assignee ID |
{"orgId": "e.g. 12345678","ticketId": "e.g. 46000000009001","subject": "e.g. Quick update","status": "{{trigger.status}}","priority": "{{trigger.priority}}"}
{"id": "46000000009001","status": "Closed","priority": "High"}
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.