Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

View Filter → Delete Undefined

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the View Filter resource and the Delete Undefined operation, it deletes a view filter identified by its ID. This is useful in scenarios where you want to programmatically clean up or remove obsolete or undefined filters from your Halo PSA system.

Practical examples include:

  • Automating cleanup of unused or invalid view filters.
  • Managing filters dynamically based on external triggers or workflows.
  • Integrating Halo PSA filter management into broader IT service management automation.

Properties

Name Meaning
Id The numeric identifier of the View Filter to delete. This property is required.

Output

The node outputs JSON data representing the response from the Halo PSA API after attempting to delete the specified view filter. The output structure typically contains confirmation of deletion or error details if the operation failed.

If the operation fails and "Continue On Fail" is enabled, the output JSON 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

  • Common issues:

    • Missing or invalid credentials will cause the node to throw an error stating "No credentials returned!".
    • Providing an invalid or non-existent View Filter ID may result in an API error indicating the resource was not found.
    • Network connectivity issues can cause request failures.

  • Error messages and resolutions:

    • "No credentials returned!": Ensure that the API key credential is properly configured and connected in n8n.
    • "Resource View Filter not found" or "Operation Delete Undefined not found for resource View Filter": Verify that the resource and operation names are correctly set.
    • API errors returned in the JSON output under the error field: Check the validity of the ID and API permissions.
    • If the node stops execution on error, consider enabling "Continue On Fail" to handle errors gracefully within workflows.

Links and References

Discussion