Actions32
- Contatos Actions
- Oportunidades Actions
- Tarefas Actions
- Produtos Actions
- Funis Actions
- Campos Personalizados Actions
- Notas Actions
- Anexos Actions
- Propostas Actions
- Webhooks Actions
Overview
The node integrates with the Linqer CRM API to manage webhooks. Specifically, the "Atualizar" (Update) operation for the "Webhooks" resource allows users to update an existing webhook's details such as its name, URL, event trigger, instance name, and timestamp.
This node is beneficial in scenarios where you need to programmatically modify webhook configurations in Linqer CRM, for example:
- Updating the callback URL of a webhook after changing your receiving endpoint.
- Changing the event that triggers the webhook to reflect new business logic.
- Adjusting metadata like the instance name or timestamp for tracking purposes.
Practical example: Suppose you have a webhook set up to notify your system when a contact is created, but now you want it to trigger on contact updates instead. Using this node, you can update the webhook's event property without manually editing it in the Linqer CRM interface.
Properties
| Name | Meaning |
|---|---|
| Nome | The name of the webhook. |
| URL | The URL endpoint where the webhook will send its payload. |
| Evento | The event name that triggers the webhook. |
| Nome da Instância | The name of the instance associated with the webhook (optional). |
| Timestamp | The timestamp related to the webhook (optional). |
| ID do Webhook | The unique identifier of the webhook to update (required). |
Output
The node outputs JSON data representing the updated webhook object returned by the Linqer CRM API. This typically includes the webhook's properties such as its ID, name, URL, event, instance name, timestamp, and any other metadata provided by the API.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Linqer CRM API.
- The node makes HTTP requests to the Linqer CRM API endpoints under
/v1/webhooks/public. - Proper configuration of the API URL and authentication credentials within n8n is necessary.
Troubleshooting
Common issues:
- Invalid or missing webhook ID: Ensure the "ID do Webhook" property is correctly set to an existing webhook's ID.
- Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- Incorrect URL format: The "URL" property must be a valid URL; otherwise, the API may reject the request.
- Missing required fields: "Nome", "URL", and "Evento" are required; omitting them may cause errors.
Error messages:
"Operação "update" não suportada para webhooks": Indicates an unsupported operation was requested; ensure the operation is set to "update".- API response errors (e.g., 400 Bad Request, 401 Unauthorized): Check the input parameters and credentials.
Resolution tips:
- Double-check all required input fields.
- Confirm the webhook ID exists in Linqer CRM.
- Review API credentials and permissions.
- Validate URLs and event names against Linqer CRM documentation.
Links and References
- Linqer CRM API Documentation (general reference for webhook endpoints):
(No direct link available from source code; please consult Linqer CRM official docs)