List Agents: Freshdesk 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. e.g. "1"
Per Page per_page	string	Optional	Results per page (max 100)

Sample request

{
  "page": "1",
  "per_page": "30"
}

Returns

[
  {
    "id": 1001,
    "contact": {
      "name": "Jane Smith",
      "email": "jane@company.com",
      "active": true
    },
    "role_ids": [
      1
    ],
    "available": true,
    "group_ids": [
      101,
      102
    ],
    "created_at": "2024-01-01T00:00:00Z",
    "ticket_scope": 1
  }
]

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about List Agents.

What does the List Agents action do in Freshdesk?

Lists all agents in Freshdesk with their email, role, and groups. Used to populate an assignee picker or to feed agent rosters into routing automation.

What inputs does List Agents require?

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

Yes. Run List Agents inside a Loop node to process arrays. Tiny Command handles Freshdesk's rate limits automatically so you don't have to throttle manually.

More actions