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 interacts with the HaloPSA API to retrieve detailed information about a specific webhook event by its unique identifier (UUID). It is useful in scenarios where you need to fetch the status, payload, or metadata of a particular webhook event that was previously triggered or logged within the HaloPSA system.
Practical examples include:
- Auditing or troubleshooting webhook deliveries by fetching event details.
- Integrating webhook event data into workflows for conditional processing.
- Monitoring webhook events for compliance or logging purposes.
Properties
| Name | Meaning |
|---|---|
| Webhook Event ID | The UUID of the webhook event to retrieve. |
| Additional Options | Include Details: Whether to include extra related objects in the response (true/false). |
Output
The node outputs JSON data representing the webhook event identified by the provided UUID. This includes core event information such as timestamps, status, and possibly the payload or metadata associated with the webhook event.
If the "Include Details" option is enabled, the output will contain additional nested objects providing more context or related data about the webhook event.
The node does not output binary data.
Dependencies
- Requires an active connection to the HaloPSA API via an API key credential configured in n8n.
- The node depends on the HaloPSA API being accessible and the provided webhook event ID being valid.
- No other external dependencies are required.
Troubleshooting
- Invalid or missing Webhook Event ID: Ensure the UUID provided is correct and corresponds to an existing webhook event in HaloPSA.
- API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions to access webhook event data.
- Network or connectivity issues: Confirm that n8n can reach the HaloPSA API endpoint without firewall or proxy restrictions.
- Empty or incomplete response: If "Include Details" is enabled but no additional data appears, verify that the webhook event actually has related detail objects in HaloPSA.
Common error messages might include unauthorized access, resource not found, or invalid parameters. Resolving these typically involves checking credentials, input values, and API availability.
Links and References
- HaloPSA API Documentation (general reference for API endpoints)
- n8n documentation on Using API Credentials