Skip to content
ActionZendeskUpdated May 2026

How do I delete a Zendesk ticket?

Short answer: Drop the "ZendeskDelete Ticket" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

FieldTypeRequiredDescription
Ticket ID
ticket_id
stringRequiredZendesk ticket ID — numeric. Find via Search Tickets.
Sample request
{
"ticket_id": "e.g. 123"
}
Returns
{
"success": true
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Delete Ticket.

Any of these apps can fire this action as part of a workflow.

FAQ

Questions about Delete Ticket.

What does the Delete Ticket action do in Zendesk?
Permanently deletes a Zendesk ticket by ID. Two-step: this marks it deleted; for PII purposes you may also need to "redact" comments separately.
What inputs does Delete Ticket require?
Required: Ticket ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Zendesk returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Delete Ticket support batch operations?
Yes. Run Delete Ticket inside a Loop node to process arrays. Tiny Command handles Zendesk's rate limits automatically so you don't have to throttle manually.
More actions

Other Zendesk actions.

Send delete ticket from your workflows.

Triggered by anything in the catalog. Free tier available. No credit card.