Workflow blocks
Update Ticket
Update ticket with comment, status, tags, priority in one API call. Comment text supports markdown — see the Comment field description for the rendering contract.
zendesk/update-ticket — Update ticket with comment, status, tags, priority in one API call. Comment text supports markdown — see the Comment field description for the rendering contract.
Where it appears
The Update Ticket block lives in the Integrations group of the Workflow Builder. Connect the Zendesk integration before adding it.
Fields
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
ticketId | text (supports references) | Yes | — | Numeric Zendesk ticket ID to update. Use a literal number or <StepName.field> to reference an ID from upstream. |
actions | actions | No | — | What this update should change on the ticket. Each action sets one property; status, priority, type, tags, and the comment can each be added once. |
Inputs and outputs
Inputs are the configurable fields above. The block produces these outputs:
Outputs
Reference an output downstream with <Update Ticket.field>.
| Name | Type | Description |
|---|---|---|
success | boolean | Success status |
ticket | json | Updated ticket (object — fields: id, subject, description, status, priority, type, tags, requester_id, assignee_id, group_id, custom_fields, created_at, updated_at) |
error | string | Error message if failed |
Example
A minimal configuration for this block:
{
"type": "zendesk/update-ticket",
"config": {
"ticketId": "<PreviousStep.field>"
}
}Limits and failure modes
- Requires a connected Zendesk integration. Calls fail if that integration is disconnected or its authorization has expired.
- Required field (
ticketId) must be set, or the block fails validation before it runs. - On failure the
erroroutput is populated; downstream blocks that reference other outputs may not receive values.