ActionFreshserviceUpdated September 2026
Who are the Freshservice agents?
Short answer: You can list freshservice agents in Freshservice by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Freshservice List Freshservice Agents action to a workflow, map its 1 input from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 |
|---|---|---|---|
Per Page per_page | string | Optional | Per Page. e.g. "30" |
Sample request
{"per_page": "30"}
Returns
{"agents": [{"id": 1,"email": "john@company.com","active": true,"last_name": "Doe","first_name": "John"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for List Freshservice Agents.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about List Freshservice Agents.
What does the List Freshservice Agents action do in Freshservice?
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.
What inputs does List Freshservice Agents require?
List Freshservice Agents 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 Agents support batch operations?
Run List Freshservice Agents 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
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.
ActionCreate 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.
ActionDelete Freshservice Ticket
Removes a ticket (soft delete in most configurations). For "duplicate ticket cleanup" or "spam filtering" maintenance workflows.
ActionGet Freshservice Ticket
Returns a ticket by ID with full detail — status, requester, agent, conversation history, custom fields. The standard lookup for ticket-context workflows.
ActionList Freshservice Tickets
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.
ActionUpdate 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.