Workflow blocks
Assign Ticket
Assign a ticket to an agent or group
zendesk/assign-ticket — Assign a ticket to an agent or group.
Where it appears
The Assign 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 assign. Use a literal number or <StepName.field> to reference an ID from a previous step. |
assigneeId | text (supports references) | No | — | Numeric Zendesk user ID of the agent to assign the ticket to. Use a literal ID or <StepName.field> from a previous step. |
groupId | text (supports references) | No | — | Numeric Zendesk group ID to route the ticket to. Use a literal ID or <StepName.field> from a previous step. |
Inputs and outputs
Inputs are the configurable fields above. The block produces these outputs:
Outputs
Reference an output downstream with <Assign 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/assign-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.