Halo PSA icon

Halo PSA

Consume Halo PSA API

Actions795

Licence → Delete Undefined

AI-generated

Overview

This node integrates with the Halo PSA API to perform various operations on different resources. Specifically, for the Licence resource with the Delete Undefined operation, it deletes a licence identified by its ID. This is useful in scenarios where you need to programmatically remove licences that are no longer defined or required in your system.

Practical examples include:

  • Cleaning up obsolete or invalid licence entries in your Halo PSA system.
  • Automating licence management workflows by removing licences based on certain criteria or triggers.

Properties

Name Meaning
Id The unique identifier (number) of the licence to delete. This property is required.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output JSON contains the response from the Halo PSA API after attempting to delete the specified licence. If the deletion is successful, the response typically confirms the deletion; if there is an error, 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 to access the Halo PSA API, including base URL, tenant identifier, client ID, and client secret.
  • The node uses HTTP requests to communicate with the Halo PSA API endpoints.
  • Proper configuration of these credentials within n8n is necessary for the node to function.

Troubleshooting

  • Common issues:

    • Missing or invalid credentials will cause the node to throw an error "No credentials returned!".
    • Providing an invalid licence ID may result in an API error indicating the licence was not found.
    • Network connectivity issues can cause request failures.
  • Error messages and resolutions:

    • "No credentials returned!": Ensure that the API credentials are correctly set up in n8n.
    • Errors returned from the API (e.g., licence not found): Verify that the licence ID exists and is correct.
    • JSON parsing errors: Make sure all input parameters are correctly formatted and valid.
  • The node supports continuing on failure, allowing workflows to proceed even if some deletions fail.

Links and References

Discussion