Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

N Central Details → List Of N Central Details

AI-generated

Overview

This node integrates with the Halo PSA API to retrieve detailed information related to the "N Central Details" resource, specifically supporting the operation "List Of N Central Details." It is designed to fetch lists of details from the N Central system managed within Halo PSA, which can be useful for IT service management, monitoring, or reporting workflows.

Typical use cases include:

  • Automating retrieval of device or system details managed by N Central.
  • Integrating N Central data into broader ITSM or monitoring dashboards.
  • Periodically syncing N Central details into other systems for analysis or alerting.

For example, a user might configure this node to list all monitored devices' details and then process that data downstream to generate reports or trigger alerts based on specific criteria.

Properties

Name Meaning
Includedetails A parameter controlling whether additional details are included in the response. Values depend on the API but typically indicate inclusion of extended information or related entities.

Output

The node outputs an array of JSON objects under the json field, each representing an item retrieved from the "List Of N Central Details" operation. The structure corresponds directly to the data returned by the Halo PSA API for this resource and operation, typically including fields describing N Central entities such as devices, configurations, statuses, etc.

No binary data output is indicated for this operation.

Dependencies

  • Requires valid credentials for the Halo PSA API, including base URL, tenant identifier, client ID, and client secret.
  • The node uses these credentials to authenticate requests via HTTP headers.
  • No additional external dependencies beyond the Halo PSA API and n8n's HTTP request capabilities.

Troubleshooting

  • No credentials returned!
    This error occurs if the node cannot find or access the required API credentials. Ensure that the API key credential is properly configured in n8n and assigned to the node.

  • Resource or Operation not found
    If the specified resource or operation does not exist, verify that the node parameters are correctly set to "N Central Details" and "List Of N Central Details."

  • API request errors
    Network issues, invalid credentials, or incorrect parameters may cause API request failures. Check the error message returned in the node output for details. Enabling "Continue On Fail" allows processing to continue despite individual errors.

  • Invalid parameter values
    The Includedetails property should be set according to the API's expected values. Passing unsupported or malformed values may result in errors or empty responses.

Links and References

Discussion