Actions13
Webhook → Update
AI-generatedOverview
This node updates an existing webhook in the EmailConnect system. It allows users to modify the webhook's name, URL, and optional description. This operation is useful for maintaining or changing webhook configurations without needing to delete and recreate them, such as updating the endpoint URL where email data is sent or renaming the webhook for clarity.
Use Case Examples
- Updating the URL of a webhook to point to a new endpoint after a server migration.
- Changing the friendly name of a webhook to better reflect its purpose in the email automation workflow.
- Adding or modifying the description of a webhook to provide more context for team members.
Properties
| Name | Meaning |
|---|---|
| Webhook Name or ID | The identifier of the webhook to update, chosen from a list or specified via expression. |
| Name | A friendly name for the webhook to help identify it. |
| URL | The webhook URL that will receive email data. |
| Description | An optional description providing additional details about the webhook. |
Output
JSON
jsonid- The unique identifier of the updated webhook.name- The updated friendly name of the webhook.url- The updated URL where the webhook sends email data.description- The updated description of the webhook, if provided.
Dependencies
- Requires an API key credential for EmailConnect API authentication.
Troubleshooting
- If no fields are provided to update, the node may throw an error or fail silently; ensure all required fields are set.
- Errors from the EmailConnect API such as 404 indicate the webhook ID does not exist; verify the webhook ID is correct.
- Network or authentication errors may occur if the API key credential is missing or invalid; check credential configuration.
Links
- n8n Expressions - Documentation on how to use expressions to specify dynamic values for properties.