Overview
This node manages webhooks in the RD Station CRM platform. Specifically, the "Webhook" resource with the "Listar" (List) operation allows users to retrieve a list of webhooks configured in their RD Station CRM account. It supports filtering, pagination, and sorting options to customize the returned webhook data.
Common scenarios where this node is beneficial include:
- Auditing or monitoring existing webhooks set up in RD Station CRM.
- Integrating webhook management into automated workflows.
- Fetching webhook details for synchronization or reporting purposes.
For example, a user might want to list all active webhooks related to contact creation events, sorted by creation date descending, to verify which endpoints are currently receiving notifications.
Properties
| Name | Meaning |
|---|---|
| Parâmetros de Listagem | Collection of parameters to control the listing behavior: |
| - Limite | Maximum number of webhooks to return |
| - Página | Page number of results to return |
| - Ordenação | Field to sort results by; options: "Data de Criação" (creation date), "URL" |
| - Direção da Ordenação | Sort direction; options: "Ascendente" (ascending), "Descendente" (descending) |
| - Status | Filter webhooks by status; options: "Ativo" (active), "Inativo" (inactive), "Todos" (all) |
| - Evento | Filter webhooks by event type that triggers them; options include: |
| - Negócio Criado (deal.created) | |
| - Negócio Atualizado (deal.updated) | |
| - Contato Criado (contact.created) | |
| - Contato Atualizado (contact.updated) | |
| - Tarefa Criada (task.created) | |
| - Tarefa Atualizada (task.updated) |
Output
The output is an array of JSON objects representing the webhooks retrieved from RD Station CRM. Each item corresponds to one webhook and includes its properties as returned by the API, such as ID, URL, events it listens to, status, creation date, and other metadata.
If the operation is successful, the json field contains the webhook data. If an error occurs and the node is set to continue on failure, the json field will contain an error property with the error message.
No binary data is output by this node.
Dependencies
- Requires an API key credential for RD Station CRM to authenticate requests.
- The node makes HTTP requests to the RD Station CRM API endpoint at
https://crm.rdstation.com/api/v1/webhooks. - Proper configuration of the API authentication credential within n8n is necessary.
Troubleshooting
- Missing or invalid webhook ID: When fetching a specific webhook, updating, or deleting, if the webhook ID is not provided or invalid, the node throws an error indicating the need for a valid webhook ID.
- Invalid callback URL or events: When creating a webhook, the node requires a valid callback URL and at least one event selected; otherwise, it throws an error.
- Empty update payload: When updating a webhook, if no fields are provided to update, the node throws an error requesting at least one field.
- API errors: Network issues, invalid credentials, or API rate limits may cause request failures. Check API key validity and network connectivity.
- Continue on Fail: If enabled, the node will output error messages per item instead of stopping execution.