Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Agent Check In → List Of Agent Check In

AI-generated

Overview

This node integrates with the Halo PSA API to retrieve a list of agent check-ins. It allows users to query check-in records for specific agents within optional date ranges. This is useful in scenarios such as monitoring agent activity, auditing attendance, or generating reports on agent availability over time.

For example, a support team manager could use this node to fetch all check-ins for a particular agent between two dates to analyze their work patterns or verify shift adherence.

Properties

Name Meaning
Agent Id The unique identifier of the agent whose check-in records you want to retrieve.
Start Date The start date (inclusive) to filter check-ins from. Expected as a string (e.g., "2023-01-01").
End Date The end date (inclusive) to filter check-ins up to. Expected as a string (e.g., "2023-01-31").

Output

The node outputs an array of JSON objects representing agent check-in records matching the query parameters. Each object corresponds to one check-in entry returned by the Halo PSA API.

The exact structure of each check-in record depends on the API response but typically includes fields such as timestamps, agent identifiers, and status details.

This node does not output binary data.

Dependencies

  • Requires an API key credential for authenticating with the Halo PSA API.
  • The node expects configuration of base URL, tenant ID, client ID, and client secret via credentials.
  • Network access to the Halo PSA API endpoint is necessary.

Troubleshooting

  • No credentials returned!: Indicates missing or misconfigured API authentication credentials. Ensure that the required API key credential is properly set up in n8n.
  • Resource or Operation not found: Occurs if the specified resource ("Agent Check In") or operation ("List Of Agent Check In") is invalid or misspelled. Verify property values.
  • API request errors: Could be due to invalid parameters, network issues, or API limits. Review error messages returned in the json.error field when continuing on fail.
  • Date format issues: The start and end dates should be valid strings in a format accepted by the API (commonly ISO 8601). Invalid formats may cause request failures.

Links and References

Discussion