List Tickets: Freshdesk 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
Page page	string	Optional	Page number (default 1)
Per Page per_page	string	Optional	Results per page (max 100)
Order By order_by	options	Optional	Order By. Options: Created At, Due By, Updated At
Order order_type	options	Optional	Order. Options: Descending, Ascending

Sample request

{
  "page": "1",
  "per_page": "30",
  "order_by": "{{trigger.order_by}}",
  "order_type": "{{trigger.order_type}}"
}

Returns

[
  {
    "id": 1,
    "status": 2,
    "subject": "Login issue",
    "priority": 1
  }
]

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

FAQ

Questions about List Tickets.

What does the List Tickets action do in Freshdesk?

Lists tickets in Freshdesk (first page, up to 30 per page). For complex queries use Search Tickets; this action is best for unfiltered queue snapshots.

What inputs does List Tickets require?

List Tickets has no required inputs. Sensible defaults are applied if you leave fields blank.

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 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 List Tickets support batch operations?

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

More actions