Actions68
- Client Actions
- Agent Actions
- Asset Actions
- Field Info Actions
- Invoice Actions
- Site Actions
- Ticket Actions
- Ticket Status Actions
- Ticket Type Actions
- Timesheet Actions
- Timesheet Event Actions
- Webhook Actions
- Webhook Event Actions
Overview
This node integrates with the HaloPSA API to manage various resources, including webhooks. Specifically, the "Webhook" resource with the "Delete" operation allows users to delete an existing webhook by specifying its unique identifier (UUID). This is useful for automating the cleanup or management of webhooks within HaloPSA, such as removing obsolete or unused webhooks programmatically.
Practical examples include:
- Automatically deleting a webhook when a related integration is disabled.
- Cleaning up test webhooks created during development.
- Managing webhook lifecycle in bulk via workflows.
Properties
| Name | Meaning |
|---|---|
| Webhook ID | The UUID of the webhook to delete. This uniquely identifies which webhook will be removed from the system. |
Output
The node outputs JSON data representing the result of the delete operation. Typically, this would confirm whether the deletion was successful or provide details if it failed. The exact structure depends on the API response but generally includes status information.
There is no indication that this node outputs binary data.
Dependencies
- Requires an active connection to the HaloPSA API using an API key or token configured in n8n credentials.
- The node relies on the HaloPSA API endpoint responsible for webhook management.
- No additional external services are required beyond the HaloPSA API.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Webhook ID will likely cause the API to return an error indicating the webhook could not be found.
- Missing or incorrect API authentication credentials will result in authorization errors.
- Network connectivity problems can prevent the node from reaching the HaloPSA API.
Error messages and resolutions:
- "Webhook not found": Verify the Webhook ID is correct and exists in your HaloPSA instance.
- "Unauthorized" or "Authentication failed": Check that the API key/token credential is correctly set up and has sufficient permissions.
- Timeout or network errors: Ensure stable internet connection and that the HaloPSA API endpoint is reachable.
Links and References
- HaloPSA API Documentation (general reference for API endpoints and usage)
- n8n documentation on creating custom nodes for further customization guidance