Workflow blocks
Close Ticket
Mark a ticket as solved with optional closing message
zendesk/close-ticket — Mark a ticket as solved with optional closing message.
Where it appears
The Close 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 mark as solved. Use a literal number or <StepName.field> to reference an ID from a previous step. |
addComment | text (multi-line, supports references) | No | — | Markdown is rendered to Zendesk HTML: bold, lists (- ), blockquotes (> ), links ([label](url)). Single newlines preserved. |
isPublic | select | No | true | Whether the closing message is posted as a public reply visible to the customer or as an internal note visible to agents only. Options: true, false. |
Inputs and outputs
Inputs are the configurable fields above. The block produces these outputs:
Outputs
Reference an output downstream with <Close Ticket.field>.
| Name | Type | Description |
|---|---|---|
success | boolean | Success status |
ticket | json | Closed 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/close-ticket",
"config": {
"ticketId": "<PreviousStep.field>",
"isPublic": "true"
}
}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.