ActionFreshdeskUpdated September 2026

How do I list Freshdesk tickets?

Short answer: You can list tickets in Freshdesk by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Freshdesk List Tickets action to a workflow, map its 4 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

List Tickets in Freshdesk — start free All 15 Freshdesk actions

List Tickets in Freshdesk — start free

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.

Triggered by

Apps that pair well as the trigger for List Tickets.

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

Google Sheets → Freshdesk

2 Google Sheets triggers

HubSpot → Freshdesk

18 HubSpot triggers

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

Run List Tickets 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