ActionFreshserviceUpdated September 2026

How do I list Freshservice tickets?

Short answer: You can list freshservice tickets in Freshservice by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Freshservice List Freshservice 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 Freshservice Tickets in Freshservice — start free All 7 Freshservice actions

List Freshservice Tickets in Freshservice — 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 (starts at 1)
Per Page per_page	string	Optional	Results per page (max 100)
Filter filter	options	Optional	Pre-defined filter to apply
Order order_type	options	Optional	Order. Options: Descending, Ascending

Sample request

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

Returns

{
  "tickets": [
    {
      "id": 1,
      "status": 2,
      "subject": "Laptop not working",
      "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 Freshservice Tickets.

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

Google Sheets → Freshservice

2 Google Sheets triggers

HubSpot → Freshservice

18 HubSpot triggers

FAQ

Questions about List Freshservice Tickets.

What does the List Freshservice Tickets action do in Freshservice?

Paginated tickets with filters by status, priority, requester, agent, group, time range. For "open critical tickets" dashboards or "all tickets I'm the agent on" personal queues.

What inputs does List Freshservice Tickets require?

List Freshservice 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 Freshservice returns an error?

The run history shows the failed step with its input and the error message Freshservice 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 Freshservice Tickets support batch operations?

Run List Freshservice 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 Freshservice's rate limits.

More actions