List Agents

halopsa.list_agents
ActionBusiness appsconnection required

Calls the HaloPSA API with the connection's credentials.

List the agents on the Halo instance.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
HaloPSA
Secret shape
{"client_id": "…", "client_secret": "…"} or {"client_id": "…", "refresh_token": "…"}
Config it needs
base_url, auth_url, tenant, scope
Resolved by
config.connection_id, else node.connection_id

Configuration

4 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
search
Only return agents whose name, email address or telephone number matches this search string.
stringNo——jane
team
Only return agents in this team, by the team's name.
stringNo——Service Desk
client_id
Only return agents who have access to this client, by its numeric id.
stringNo——12
include_disabled
Include disabled agents in the response.
booleanNofalse——

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "client_id": "12",
  "include_disabled": false,
  "search": "jane",
  "team": "Service Desk"
}

Output

One shape.

result

FieldTypeExample
items
The records Halo returned on this page.
array—
count
How many records this response carried.
number—
record_count
How many records match in total, as Halo reported; equal to count on a listing that is not paginated.
number—
{
  "count": 0,
  "items": [],
  "record_count": 0
}

See List Agents run in a workflow.

In a technical demo we add the HaloPSA connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.