Overview
This node manages webhooks in the RD Station CRM platform, specifically allowing users to update existing webhooks. It is useful for scenarios where you need to modify webhook configurations such as callback URLs, subscribed events, status, data format, or HTTP headers without recreating the webhook from scratch.
Practical examples include:
- Changing the callback URL to a new endpoint after migrating your backend.
- Adding or removing events that trigger the webhook notifications.
- Activating or deactivating a webhook temporarily.
- Switching the payload format between JSON and XML.
- Adding custom HTTP headers for authentication or other purposes.
Properties
| Name | Meaning |
|---|---|
| ID do Webhook | The unique identifier of the webhook to be updated. |
| Dados do Webhook | Collection of fields to update on the webhook: |
| - URL de Callback | The new callback URL where webhook notifications will be sent. (Required) |
| - Eventos | List of events that will trigger the webhook. Options: "Negócio Criado", "Negócio Atualizado", "Contato Criado", "Contato Atualizado", "Tarefa Criada", "Tarefa Atualizada". (At least one required) |
| - Status | Status of the webhook: "Ativo" (active) or "Inativo" (inactive). Active webhooks send notifications. |
| - Formato de Entrega | Format of the data sent to the callback URL: "JSON" or "XML". |
| - Cabeçalhos HTTP | Custom HTTP headers to include with the webhook request. Each header has a name and value. |
Output
The node outputs a JSON object representing the updated webhook details returned by the RD Station CRM API. This includes all relevant webhook properties after the update.
If the operation is successful, the output JSON contains the updated webhook data.
If the webhook is deleted (not applicable here but part of the node), the output confirms success with a message.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the RD Station CRM API.
- The node uses the base API URL
https://crm.rdstation.com/api/v1. - Proper configuration of the API credential in n8n is necessary for successful requests.
Troubleshooting
- Missing Webhook ID: If the webhook ID is not provided or invalid, the node throws an error stating that a valid webhook ID is required.
- Missing Required Fields: When updating, if no fields are provided to update, the node throws an error indicating at least one field must be specified.
- Missing Callback URL or Events: If the callback URL or events list is empty when required, errors are thrown.
- API Authentication Errors: Ensure the API key credential is correctly set up and has permissions to manage webhooks.
- Network Issues: Connectivity problems with the RD Station CRM API can cause request failures.
- To handle errors gracefully, enable "Continue On Fail" in the node settings to process subsequent items even if some fail.