Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

View Lists → Post Undefined

AI-generated

Overview

This node integrates with the Halo PSA API, allowing users to perform various operations on different resources within the Halo PSA system. Specifically, for the "View Lists" resource and the "Post Undefined" operation, it sends a POST request with a JSON body to create or update view lists based on provided filters and translations.

Common scenarios where this node is beneficial include automating the management of custom views or filtered lists in Halo PSA, such as dynamically updating list filters or localizations without manual intervention. For example, a user might automate the creation of filtered ticket views or customized dashboards by specifying filter criteria and translations programmatically.

Properties

Name Meaning
Body A JSON object representing the payload sent in the POST request. It includes:
- filters: An array of filter objects, each containing filter_values and multiselect_value arrays.
- translations: An array of translation objects.
This property allows full customization of the view list's filters and translations.

The Body property expects a JSON structure similar to:

{
  "filters": [
    {
      "filter_values": [{}],
      "multiselect_value": [{}]
    }
  ],
  "translations": [{}]
}

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output item contains:

  • json: The parsed JSON response from the Halo PSA API after performing the POST operation on the "View Lists" resource.
  • If an error occurs and the node is configured to continue on failure, the output will contain an error field with the error message.

No binary data output is produced by 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 API requests via HTTP headers.
  • No additional external dependencies beyond the Halo PSA API and n8n's HTTP request capabilities.

Troubleshooting

  • No credentials returned!: Indicates missing or invalid API credentials. Ensure that the required API authentication details are correctly configured in n8n.
  • Resource not found: Occurs if the specified resource ("View Lists") is not recognized. Verify the resource name is correct.
  • Operation not found for resource: Happens if the operation ("Post Undefined") does not exist for the given resource. Confirm the operation name matches the available options.
  • JSON parsing errors: Since the Body property expects valid JSON, malformed JSON input will cause errors. Validate JSON syntax before running the node.
  • API request failures: Network issues, incorrect endpoint URLs, or insufficient permissions can cause request errors. Check API connectivity and credentials.
  • When continueOnFail is enabled, errors are captured in the output rather than stopping execution, which helps in debugging batch operations.

Links and References

Discussion