Actions84
- Broadcast Actions
- Contact Actions
- Contact Property Actions
- Domain Actions
- Email Actions
- Event Actions
- Log Actions
- Receiving Email Actions
- Segment Actions
- Template Actions
- Topic Actions
- Webhook Actions
- Workflow Actions
Webhook → Update
AI-generatedOverview
This node updates an existing webhook in the Resend email platform. It allows users to modify the webhook's endpoint URL, the email events that trigger the webhook, and the webhook's status (enabled or disabled). This is useful for managing how and when webhook notifications are received, such as changing the destination URL for webhook events or enabling/disabling the webhook without deleting it.
Use Case Examples
- Updating the endpoint URL of a webhook to a new HTTPS URL to receive event notifications at a different server.
- Changing the events that trigger the webhook notifications, for example, to only receive notifications for 'email.sent' events.
- Disabling a webhook temporarily to stop receiving event notifications without deleting the webhook.
Properties
| Name | Meaning |
|---|---|
| Webhook | The unique identifier of the webhook to update. This ID is obtained from the Create Webhook response or List Webhooks operation. |
| Update Fields | Fields to update on the webhook, including endpoint URL, events to trigger notifications, and status. |
Output
JSON
webhookId- The unique identifier of the updated webhook.endpoint- The updated HTTPS URL endpoint of the webhook.events- The list of email events that trigger the webhook notifications.status- The current status of the webhook, either enabled or disabled.
Dependencies
- Requires an API key credential for the Resend email platform to authenticate and authorize the update operation.
Troubleshooting
- Ensure the webhook ID provided is valid and exists; otherwise, the update operation will fail.
- The endpoint URL must be a valid HTTPS URL accessible from the internet; otherwise, webhook notifications will not be delivered.
- If the webhook is disabled, no event notifications will be sent, which might be mistaken for a failure.
- Common errors may include authentication failures if the API key is invalid or missing, or validation errors if required fields are missing or incorrectly formatted.