Workflow blocks
Create Ticket
Create a new Zendesk ticket
zendesk/create-ticket — Create a new Zendesk ticket.
Where it appears
The Create Ticket block lives in the Integrations group of the Workflow Builder. Connect the Zendesk integration before adding it.
Fields
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
subject | text (supports references) | Yes | — | Subject line for the new Zendesk ticket. Use literal text or <StepName.field> to reference a value from a previous step. |
description | text (multi-line, supports references) | Yes | — | Body of the new ticket, used as the first comment. Use literal text or <StepName.field> to reference a value from a previous step. |
actions | actions | No | — | Optional ticket fields to set when creating the ticket. Each action sets one property; requester, priority, type, and tags can each be added once. Options: setRequester, setPriority, setTicketType, addTags, setCustomField. |
Inputs and outputs
Inputs are the configurable fields above. The block produces these outputs:
Outputs
Reference an output downstream with <Create Ticket.field>.
| Name | Type | Description |
|---|---|---|
success | boolean | Success status |
ticket | json | Created 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/create-ticket",
"config": {
"subject": "<PreviousStep.field>",
"description": "<PreviousStep.field>"
}
}Limits and failure modes
- Requires a connected Zendesk integration. Calls fail if that integration is disconnected or its authorization has expired.
- Required fields (
subject,description) 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.