Actions39
- Contact Actions
- Transaction Actions
- Subscription Actions
- Affiliation Actions
- Checkout Actions
- Country Actions
- Coupon Actions
- Product Actions
- User Actions
- Webhook Actions
Overview
This node allows interaction with the Guru Digital Manager API to manage various resources such as contacts, transactions, subscriptions, and webhooks. Specifically for the Webhook - Delete operation, it enables users to delete a webhook by its ID from their Guru Digital Manager account.
Typical use cases include:
- Automating the removal of obsolete or unwanted webhooks.
- Managing webhook lifecycle programmatically within workflows.
- Cleaning up webhooks that are no longer needed to avoid unnecessary event triggers.
For example, if you have a webhook set up to listen to certain events but want to disable it permanently, this node can delete it by specifying its unique webhook ID.
Properties
| Name | Meaning |
|---|---|
| Webhook ID | The unique identifier of the webhook to be deleted. This is required. |
Output
The output JSON contains an object indicating the success of the deletion operation. It typically looks like:
{
"success": true,
"message": "Webhook deleted successfully"
}
This confirms that the webhook was removed from the system. No binary data is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Guru Digital Manager API.
- The base URL for the API is configurable via credentials; defaults to
https://digitalmanager.guru/api/v2. - The node uses HTTP requests to communicate with the API endpoints.
Troubleshooting
- Missing Credentials Error: If the API key or user token is not provided or invalid, the node will throw an error stating that credentials are required. Ensure valid API authentication is configured.
- Invalid Webhook ID: If the specified webhook ID does not exist or is incorrect, the API may return an error. Verify the webhook ID before attempting deletion.
- API Endpoint Issues: Network issues or incorrect base URL configuration can cause request failures. Confirm the base URL and network connectivity.
- Permission Errors: The API token must have sufficient permissions to delete webhooks. Lack of permission will result in authorization errors.
- Continue on Fail: If enabled, the node will continue processing other items even if one deletion fails, returning the error message in the output.
Links and References
- Guru Digital Manager API Documentation: https://docs.digitalmanager.guru/developers/webhooks
- n8n HTTP Request Helper: https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httpRequest/
