Actions51
- Platforms Actions
- Projects Actions
- Webhooks Actions
- ApiKeys Actions
- Auth Actions
- Identities Actions
- Members Actions
- Messages Actions
- Platform Logs Actions
Overview
This node operation updates an existing webhook configuration within a specified project. It allows users to modify properties such as the webhook's name, URL, subscribed events, and activation status. This is useful for managing event notifications dynamically without needing to recreate webhooks from scratch.
Typical use cases include:
- Changing the target URL where webhook events are sent.
- Updating the list of events the webhook listens to (e.g., message received, reaction added).
- Enabling or disabling the webhook temporarily.
- Renaming the webhook for better identification.
For example, if you have a webhook that sends notifications to a specific endpoint but need to change it to a new URL or adjust which events trigger the webhook, this operation facilitates those updates seamlessly.
Properties
| Name | Meaning |
|---|---|
| Webhook ID | The unique identifier of the webhook to update (required). |
| New webhook name | The new friendly name for the webhook (optional). |
| New webhook URL | The new target URL where webhook events will be delivered (optional). |
| New events subscription | Comma-separated list of event types to subscribe to (optional). Examples: message.received,message.sent |
| Enable or disable webhook | Boolean flag to activate (true) or deactivate (false) the webhook (optional). |
| Project | Identifier of the project containing the webhook (required). |
Output
The output JSON contains the updated webhook object returned by the API after the update operation. This typically includes fields such as the webhook ID, name, URL, subscribed events, active status, and possibly delivery statistics or metadata.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential configured in n8n to authenticate requests against the GateKit API.
- The node uses the base URL provided by the credential to send HTTP PATCH requests to update webhook configurations.
- The user must specify the project identifier and webhook ID to target the correct resource.
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 is correct.
- Insufficient Permissions: Ensure the API key used has permissions to update webhooks in the specified project.
- Invalid URL Format: When updating the webhook URL, ensure it is a valid URL format; otherwise, the API may reject the request.
- Empty Update: If no optional fields (name, url, events, isActive) are provided, the update request might do nothing or return an error. Provide at least one field to update.
- Project Not Found: Confirm the project identifier exists and is accessible with the current credentials.