List Employees: Zoho People 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
Start Index sIndex	string	Optional	Start Index. e.g. "1"
Limit limit	string	Optional	Limit. e.g. "200"
Search Field searchField	string	Optional	Search Field. Example: Employeestatus
Search Value searchValue	string	Optional	Search Value. Example: Active

Sample request

{
  "sIndex": "1",
  "limit": "200",
  "searchField": "e.g. Employeestatus",
  "searchValue": "e.g. Active"
}

Returns

{
  "response": {
    "result": [
      {
        "EmailID": "john@company.com",
        "LastName": "Doe",
        "FirstName": "John",
        "EmployeeID": "EMP001",
        "Employeestatus": "Active"
      }
    ],
    "status": 0,
    "message": "Data fetched successfully"
  }
}

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

FAQ

Questions about List Employees.

What does the List Employees action do in Zoho People?

Lists employees from Zoho People with their employment, department, and contact fields. Used for HRIS sync or directory exports.

What inputs does List Employees require?

List Employees 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 Zoho People 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 Employees support batch operations?

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

More actions