Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Type Info → List Of Xtype

AI-generated

Overview

This node integrates with the Halo PSA API to retrieve a list of "xtype" entities under the "Type Info" resource. It allows users to query and filter these types based on various parameters such as asset group, ticket type, and other flags. This operation is useful for scenarios where you need to dynamically fetch and work with different classification or categorization types defined in Halo PSA, for example, when automating asset management, ticketing workflows, or configuration setups.

Practical examples include:

  • Fetching all types related to a specific asset group to populate dropdowns in forms.
  • Filtering types that can only be created or edited by certain roles.
  • Including or excluding current types based on business logic.

Properties

Name Meaning
Assetgroup Id Filter types by a specific asset group identifier.
Can Create Only Filter to include only types that can be created (boolean flag).
Can Edit Only Filter to include only types that can be edited (boolean flag).
Fixedassetgroups Filter types related to fixed asset groups.
Include Current Flag to include current types in the results (boolean flag).
Resourcesonly Filter to include only resource-related types (boolean flag).
Setuplist Filter types based on a setup list parameter.
Tickettype Id Filter types by a specific ticket type identifier.
Type Filter types by a string representing the type category or name.

All properties are sent as query parameters to the API request.

Output

The node outputs an array of JSON objects, each representing a type entity retrieved from the Halo PSA API. The exact structure depends on the API response but generally includes details about each xtype such as identifiers, names, and associated metadata.

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 containing base URL, tenant ID, client ID, and client secret for authentication.
  • No additional external dependencies beyond the configured API credentials.

Troubleshooting

  • No credentials returned!: Ensure that the API key credential is properly configured and connected in n8n.
  • Resource or Operation not found: Verify that the selected resource is "Type Info" and operation is "List Of Xtype".
  • API request errors: Check network connectivity and validity of query parameters. Invalid or missing parameters may cause the API to reject the request.
  • JSON parsing errors: If using advanced JSON parameters, ensure they are correctly formatted.

If the node is set to continue on fail, errors will be returned in the output JSON under an error field for each failed item.

Links and References

Discussion