Short answer: Drop the "Zoho Desk → Create 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 |
Subject subject | string | Required | Subject. Example: Cannot access my account |
Department ID departmentId | string | Required | Department ID. Example: 46000000001234 |
Description description | string | Optional | Description |
Requester Email email | string | Optional | Requester Email. e.g. "customer@example.com" |
Priority priority | options | Optional | Priority. Options: Low, Medium, High, Urgent |
Status status | options | Optional | Status. Options: Open, On Hold, Escalated, Closed |
Assignee ID assigneeId | string | Optional | Assignee ID. Example: 46000000005678 |
{"orgId": "e.g. 12345678","subject": "e.g. Cannot access my account","departmentId": "e.g. 46000000001234","description": "{{trigger.description}}","email": "customer@example.com"}
{"id": "46000000009001","status": "Open","subject": "Cannot access my account","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.