ActionFreshdeskUpdated September 2026
How do I delete a Freshdesk ticket?
Short answer: You can delete ticket in Freshdesk by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Freshdesk 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 | Ticket ID. Example: 123 |
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 Freshdesk?
Deletes a Freshdesk ticket by ID. Tickets move to trash for 30 days before permanent deletion, so this is recoverable in the short term.
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 Freshdesk returns an error?
The run history shows the failed step with its input and the error message Freshdesk 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 Freshdesk's rate limits.
More actions
Other Freshdesk actions.
Action
Add Note to Ticket
Adds a note (private or public) or a reply to an existing Freshdesk ticket. Used for AI-summary notes, automated status updates, or piping context from external systems.
ActionCreate Company
Creates a new company (B2B customer account) in Freshdesk. Used to mirror your CRM accounts into the helpdesk so contacts auto-link.
ActionCreate Contact
Creates a new contact (end-customer) in Freshdesk with name, email, phone, company, and tags. Used to provision contacts before ticket creation.
ActionCreate Ticket
Creates a new support ticket in Freshdesk with requester, subject, description, source, priority, status, group, and agent. The entry point for converting external alerts or forms into trackable tickets.
ActionDelete Contact
Deletes a Freshdesk contact by ID. Note that this hides the contact rather than permanently removing them, so their tickets are preserved.
ActionGet Contact
Returns a Freshdesk contact by ID with their email, phone, company, and custom fields. Used to enrich trigger payloads or render contact UI.