List Users: Zendesk 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
Role role	options	Optional	Role. Options: All, End Users, Agents, Admins
Per Page per_page	string	Optional	Per Page. e.g. "100"

Sample request

{
  "role": "{{trigger.role}}",
  "per_page": "100"
}

Returns

{
  "count": 42,
  "users": [
    {
      "id": 123,
      "name": "John Doe",
      "role": "end-user",
      "email": "john@example.com"
    }
  ]
}

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

FAQ

Questions about List Users.

What does the List Users action do in Zendesk?

Lists users in Zendesk, optionally filtered by role (end-user, agent, admin). Used for directory exports or for sync into your auth/CRM system.

What inputs does List Users require?

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

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

More actions