Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

User Change → List Of User Change

AI-generated

Overview

This node integrates with the Halo PSA API to retrieve a list of user changes. It is designed to fetch detailed records about modifications made to users within the Halo PSA system, such as updates to user profiles or status changes. This functionality is useful for auditing, synchronization, or monitoring user activity in an automated workflow.

Typical use cases include:

  • Automatically syncing user change logs from Halo PSA into other systems.
  • Triggering alerts or actions based on specific user changes.
  • Generating reports on user modifications over time.

Properties

Name Meaning
Change Date Filter user changes by a specific date.
Count Limit the number of user change records returned.
Exclude Generaluser Option to exclude general user entries from the results.
Idonly Return only the IDs of the user changes instead of full details.
Order Primary field to order the results by.
Order 2 Secondary ordering field.
Order 3 Tertiary ordering field.
Order 4 Fourth-level ordering field.
Order 5 Fifth-level ordering field.
Orderdesc Boolean or flag to specify descending order for the primary order field.
Orderdesc 2 Descending order flag for the secondary order field.
Orderdesc 3 Descending order flag for the tertiary order field.
Orderdesc 4 Descending order flag for the fourth-level order field.
Orderdesc 5 Descending order flag for the fifth-level order field.
Page No Specify which page of results to retrieve (pagination).
Page Size Number of records per page to return.
Pageinate Enable or disable pagination.

All these properties are sent as query parameters to the API request when listing user changes.

Output

The node outputs an array of JSON objects representing user change records retrieved from the Halo PSA API. Each item corresponds to one user change entry and contains all relevant data fields as provided by the API.

If the idonly property is used, the output will contain only the IDs of the user changes rather than full detail objects.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Halo PSA API via an API key credential.
  • The node expects credentials that provide base URL, tenant identifier, client ID, and client secret for authentication.
  • Proper configuration of these credentials in n8n is necessary for successful API communication.

Troubleshooting

  • No credentials returned!: This error indicates missing or misconfigured API credentials. Ensure the API key credential is set up correctly in n8n.
  • Resource or Operation not found: Occurs if the specified resource or operation name does not match the available options. Verify the spelling and case of "User Change" and "List Of User Change".
  • API request failures: Network issues, invalid parameters, or permission problems can cause errors. Check the API response message included in the error output for clues.
  • When using pagination, ensure that page_no and page_size values are valid integers to avoid unexpected results.
  • If filtering by change_date, confirm the date format matches the API expectations.

Links and References

Discussion