Actions52
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
- Platforms Actions
- Projects Actions
- Webhooks Actions
Overview
This node provides integration with a universal messaging gateway platform, allowing users to manage various resources such as API keys, identities, messages, platforms, projects, and webhooks. Specifically, the Webhooks - Delete operation enables users to delete an existing webhook from a specified project. This is useful for cleaning up or removing obsolete webhook configurations that are no longer needed for event notifications.
Typical use cases include:
- Removing webhooks that are no longer in use to prevent unnecessary event traffic.
- Managing webhook lifecycle programmatically within automation workflows.
- Maintaining security by deleting webhooks that may have been compromised or deprecated.
Example: A user wants to delete a webhook identified by its ID from their "default" project to stop receiving event notifications on that webhook URL.
Properties
| Name | Meaning |
|---|---|
| Webhook ID | The unique identifier of the webhook to be deleted. |
| Project | The project identifier under which the webhook exists. Typically used to scope the API call. |
Note: The provided properties JSON includes some duplicate entries for "Webhook ID" with slightly different naming ("webhookId" vs "WebhookId") but they all represent the same required string input for identifying the webhook.
Output
The node outputs the response from the API after attempting to delete the webhook. Typically, this will be a confirmation of deletion or an empty success response. The output is structured as JSON data representing the API's response.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests against the messaging gateway API.
- The node uses the base URL and authentication headers from the configured credentials.
- The project identifier must be valid and accessible by the authenticated user.
Troubleshooting
- Invalid Webhook ID: If the webhook ID does not exist or is incorrect, the API will likely return a 404 Not Found error. Verify the webhook ID before attempting deletion.
- Permission Denied: If the API key lacks permissions to delete webhooks in the specified project, a 403 Forbidden error may occur. Ensure the API key has appropriate scopes.
- Project Not Found: Using an invalid or misspelled project identifier can cause errors. Confirm the project name is correct.
- Network Issues: Connectivity problems or incorrect API URL configuration can lead to request failures. Check network access and credential settings.
Links and References
- Messaging Gateway API Documentation - Webhooks (hypothetical link)
- n8n documentation on HTTP Request Node for understanding API calls
- General webhook management best practices: https://en.wikipedia.org/wiki/Webhook
This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.