Start free
ActionFreshserviceUpdated June 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.

FieldTypeRequiredDescription
Page
page
stringOptionalPage number (starts at 1)
Per Page
per_page
stringOptionalResults per page (max 100)
Filter
filter
optionsOptionalPre-defined filter to apply
Order
order_type
optionsOptionalOrder. 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.

Gmail → Freshservice
1 Gmail triggers
Slack → Freshservice
13 Slack triggers
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 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. TinyCommand handles Freshservice's rate limits automatically so you don't have to throttle manually.
More actions

Other Freshservice actions.

Action
Add Note to Freshservice Ticket
Posts a public reply or private note to a ticket. Useful for "AI-summarised context → log as private note for the agent" patterns.
Action
Create Freshservice Ticket
Files a new IT ticket with subject, description, priority, requester, group. For "monitoring alert → auto-file ticket for the on-call team" or "user submitted via portal → create ticket" workflows.
Action
Delete Freshservice Ticket
Removes a ticket (soft delete in most configurations). For "duplicate ticket cleanup" or "spam filtering" maintenance workflows.
Action
Get Freshservice Ticket
Returns a ticket by ID with full detail — status, requester, agent, conversation history, custom fields. The standard lookup for ticket-context workflows.
Action
List Freshservice Agents
Returns every agent with role, group memberships, contact info. Useful for resolving agent IDs in routing rules or for "show me agents currently on shift" workflows.
Action
Update Freshservice Ticket
Partial update on ticket fields — status, priority, assignee, custom fields. For "auto-route to the right team based on subject keywords" workflows or for "auto-resolve aged tickets" maintenance.
List Freshservice Tickets in Freshservice — start free