Actions51
- Platforms Actions
- Projects Actions
- Webhooks Actions
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
Overview
This node provides integration with a universal messaging gateway platform, allowing users to manage various resources such as API keys, identities, members, 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 delete. |
| Project | The project identifier where the webhook exists. Defaults to "default". |
Note: The property WebhookId appears duplicated but represents the same webhook identifier parameter.
Output
The node outputs the JSON response returned by the API after attempting to delete the webhook. Typically, this will be a confirmation of deletion or an error message if the deletion failed.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authentication with the messaging gateway API.
- The node uses the base URL and headers configured via credentials.
- The project identifier must be provided to specify the scope of the webhook.
Troubleshooting
- Invalid Webhook ID: If the webhook ID does not exist or is incorrect, the API will return an error indicating the webhook was not found. Verify the webhook ID before attempting deletion.
- Permission Denied: Insufficient permissions or invalid API credentials can cause authorization errors. Ensure the API key has rights to modify webhooks in the specified project.
- Project Not Found: Using an incorrect project identifier will result in failure. Confirm the project name or ID is correct.
- Network Issues: Connectivity problems to the API endpoint will cause request failures. Check network access and API URL configuration.
Links and References
- GateKit API Documentation (generic reference, replace with actual docs if available)
- Webhook management concepts in messaging platforms (general knowledge)
This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.