List Contacts: 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	Per Page. e.g. "30"
Filter by Email email	string	Optional	Exact email match

Sample request

{
  "page": "1",
  "per_page": "30",
  "email": "e.g. user@example.com"
}

Returns

[
  {
    "id": 1001,
    "name": "John Doe",
    "email": "john@example.com",
    "active": true
  }
]

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

FAQ

Questions about List Contacts.

What does the List Contacts action do in Freshdesk?

Lists Freshdesk contacts (first page). For full sync use the search endpoint with pagination or filters; this action is best for spot-checks and pickers.

What inputs does List Contacts require?

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

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