Workflow blocks
Set Ticket Priority
Set the priority level on a Zendesk ticket (low, normal, high, or urgent).
zendesk/set-ticket-priority — Set the priority level on a Zendesk ticket (low, normal, high, or urgent).
Where it appears
The Set Ticket Priority 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 whose priority should be updated. Use a literal number or <StepName.field> to reference an ID from upstream. |
priority | select | Yes | — | Priority level to apply. Urgent triggers SLA breach notifications; use it for customer-impacting issues requiring immediate attention. Options: low, normal, high, urgent. |
Inputs and outputs
Inputs are the configurable fields above. The block produces these outputs:
Outputs
Reference an output downstream with <Set Ticket Priority.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/set-ticket-priority",
"config": {
"ticketId": "<PreviousStep.field>",
"priority": "low"
}
}Limits and failure modes
- Requires a connected Zendesk integration. Calls fail if that integration is disconnected or its authorization has expired.
- Required fields (
ticketId,priority) 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.