Delete Freshservice Ticket: Freshservice action

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	The numeric ID of the ticket to delete

Sample request

{
  "ticket_id": "e.g. 123"
}

Returns

{
  "success": true
}

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

FAQ

Questions about Delete Freshservice Ticket.

What does the Delete Freshservice Ticket action do in Freshservice?

Removes a ticket (soft delete in most configurations). For "duplicate ticket cleanup" or "spam filtering" maintenance workflows.

What inputs does Delete Freshservice 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 Freshservice 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 Freshservice Ticket support batch operations?

Yes. Run Delete Freshservice Ticket inside a Loop node to process arrays. Tiny Command handles Freshservice's rate limits automatically so you don't have to throttle manually.

More actions