Actions18
- Payment Actions
- Wallet Actions
- Line of Credit Actions
- Webhook Actions
Overview
This node integrates with the Voltage API to manage webhooks within an organization. Specifically, the Delete Webhook operation allows users to remove a webhook by specifying its ID and the organization it belongs to. This is useful for cleaning up unused or obsolete webhooks, preventing unnecessary event notifications, or managing webhook lifecycle programmatically.
Practical example:
If you have automated workflows that create webhooks dynamically for different projects or environments, you can use this node to delete those webhooks once they are no longer needed, ensuring your system remains tidy and avoids processing irrelevant events.
Properties
| Name | Meaning |
|---|---|
| Organization ID | The unique identifier of the organization under which the webhook exists. |
| Webhook ID | The unique identifier of the webhook to be deleted. |
Output
The output JSON object confirms the success of the deletion operation. It contains:
success: A boolean indicating whether the webhook was successfully deleted (true).message: A string message confirming the deletion, e.g.,"Webhook deleted successfully".
Example output:
{
"success": true,
"message": "Webhook deleted successfully"
}
No binary data is produced by this operation.
Dependencies
- Requires an active connection to the Voltage API via an API key credential.
- The node expects the Voltage API base URL and timeout settings configured in the credentials.
- Proper permissions on the API key to delete webhooks within the specified organization.
Troubleshooting
Common issues:
- Invalid or missing Organization ID or Webhook ID will cause the operation to fail.
- Insufficient permissions on the API key may result in permission errors.
- Network or server issues with the Voltage API could cause timeouts or server errors.
Error messages and resolutions:
Validation Error (422): Indicates invalid request data; verify that the Organization ID and Webhook ID are correct and properly formatted.Authentication Error (401): Check that the API key credential is valid and has not expired.Permission Error (403): Ensure the API key has rights to delete webhooks in the organization.Not Found (404): The specified organization or webhook does not exist; confirm IDs.Server Error (5xx): Temporary issue with the Voltage API; retry after some time.Failed to parse response as JSON: Usually indicates authentication or configuration issues; verify credentials and organization ID.
Links and References
- Voltage API Documentation (hypothetical link)
- n8n documentation on creating and managing webhooks (for general webhook concepts)