HaloPSA Complete

Overview

This node integrates with the HaloPSA API to manage various resources, including assets. Specifically, the "Delete Asset" operation allows users to remove an asset from their HaloPSA system by specifying its unique ID. This is useful in scenarios where assets are no longer in use, have been decommissioned, or were created erroneously and need to be cleaned up to maintain accurate records.

Practical examples include:

• Automatically deleting assets that are marked as obsolete in an external inventory system.
• Removing test or placeholder assets created during onboarding or testing phases.
• Cleaning up assets after a project completion or hardware refresh cycle.

Properties

The "Asset ID" property is a required numeric input representing the unique identifier of the asset within HaloPSA that should be deleted.

Output

The node outputs JSON data representing the response from the HaloPSA API after attempting to delete the specified asset. Typically, this will confirm whether the deletion was successful or provide error details if it failed.

If the API supports it, the output may include status codes or messages indicating the result of the delete operation.

No binary data output is involved in this operation.

Dependencies

• Requires an active connection to the HaloPSA API.
• Needs an API authentication token or key configured in n8n credentials for authorization.
• The node depends on the internal router logic (actions/router) to dispatch the delete request to the correct API endpoint.

Troubleshooting

• Common issues:

  • Providing an invalid or non-existent Asset ID will likely result in an error response from the API.
  • Missing or incorrect API credentials will cause authentication failures.
  • Network connectivity problems can prevent the node from reaching the HaloPSA API.

• Error messages:

  • "Asset not found" or similar indicates the provided Asset ID does not exist.
  • Authentication errors suggest checking the API key or token configuration.
  • Timeout or network errors require verifying internet access and API availability.

To resolve these issues:

• Double-check the Asset ID value before running the node.
• Ensure the API credentials are correctly set up and valid.
• Confirm that the HaloPSA API service is reachable from your environment.

Links and References

• HaloPSA API Documentation (general reference for API endpoints and usage)
• n8n documentation on creating custom nodes