ActionZendeskUpdated September 2026
How do I delete a Zendesk ticket?
Short answer: You can delete ticket in Zendesk by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Zendesk Delete Ticket action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Ticket ID ticket_id | string | Required | Zendesk 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 run history shows the failed step with its input and the error message Zendesk returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Delete Ticket support batch operations?
Run Delete Ticket inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Zendesk's rate limits.
More actions
Other Zendesk actions.
Action
Add Comment to Ticket
Adds a public comment (customer-visible) or internal note to an existing Zendesk ticket. Used for AI summary notes, automated status broadcasts, or piping context from external systems.
ActionCreate Organization
Creates an organization (B2B account) in Zendesk with name, domains, tags, and custom fields. Used to mirror CRM accounts into Zendesk so end-users auto-link by email domain.
ActionCreate Ticket
Creates a new support ticket in Zendesk with requester, subject, comment body, priority, status, type, group, assignee, and tags. The entry point for converting external alerts or forms into trackable tickets.
ActionCreate User
Creates a new user (customer or agent) in Zendesk with name, email, role, organization, and tags. Used to provision users before ticket creation or to mirror your auth system.
ActionDelete User
Deletes a user from Zendesk by ID. Two-step: soft-delete first; pass permanently=true (or use the dedicated permanently-delete endpoint) for GDPR right-to-delete.
ActionGet Ticket
Retrieves a Zendesk ticket by ID with subject, requester, status, priority, group, assignee, and custom fields. The standard read after a trigger fires with an ID.