Search 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
Search Query query	string	Required	Search Query. Example: email:john@example.com OR name:John

Sample request

{
  "query": "e.g. email:john@example.com OR name:John"
}

Returns

{
  "count": 1,
  "users": [
    {
      "id": 123,
      "name": "John Doe",
      "role": "agent",
      "email": "john@example.com"
    }
  ]
}

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

FAQ

Questions about Search Users.

What does the Search Users action do in Zendesk?

Searches for users in Zendesk by email, name, phone, organization, or tags. The standard upsert lookup before deciding to create or update.

What inputs does Search Users require?

Required: Search Query. Every input accepts a static value or a variable from any upstream node in your workflow.

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

Yes. Run Search 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