List Freshservice Tickets: 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
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.

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

Yes. Run List Freshservice Tickets 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