Update Ticket
zendesk.update_ticket
ActionBusiness appsconnection required
Calls the Zendesk API PUT /api/v2/tickets/{id}.json.
Update a Zendesk ticket's status, priority, or assignee.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Username & password
- Providers
- Zendesk
- Secret shape
- {"email", "api_token"}
- Config it needs
- subdomain
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
ticket_id The ticket id. Supports {{ }}. | string | Yes | — | — | — |
status New status — Zendesk accepts only the listed values. | string | No | — | one of "", "new", "open", "pending", "hold", "solved", "closed" | — |
priority urgent | high | normal | low. | string | No | — | — | — |
assignee_id Agent id to assign. | string | No | — | — | — |
Output
One shape.
ticket
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
ticket_id | string | — |
status | string | — |
{
"ok": false,
"status": "",
"ticket_id": ""
}Related Zendesk nodes
Solutions with Zendesk
See Update Ticket run in a workflow.
In a technical demo we add the Zendesk connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.