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, for the Webhooks - Create operation, it allows users to create new webhook subscriptions in Linqer CRM by specifying details such as the webhook's name, URL, event trigger, instance name, and timestamp.
This node is beneficial when you want to automate workflows triggered by specific events in Linqer CRM, such as contact updates or opportunity changes, by receiving real-time notifications via webhooks.
Practical example:
You can use this node to create a webhook that triggers whenever a new contact is added in Linqer CRM. The webhook will send data to your specified URL, enabling you to process or sync this information automatically in other systems.
Properties
| Name | Meaning |
|---|---|
| Nome | The name of the webhook being created. |
| URL | The destination URL where the webhook payloads will be sent. |
| Evento | The event name in Linqer CRM that will trigger the webhook. |
| Nome da Instância | The name of the Linqer CRM instance associated with the webhook (optional). |
| Timestamp | The timestamp associated with the webhook creation (optional). |
Output
The node outputs JSON data representing the created webhook object returned from the Linqer CRM API. This typically includes the webhook's ID, name, URL, event, instance name, timestamp, and other metadata confirming successful creation.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Linqer CRM API.
- The node uses HTTP requests to Linqer CRM endpoints under
/v1/webhooks/public. - Ensure the Linqer CRM API URL and authentication credentials are properly configured in n8n.
Troubleshooting
Common issues:
- Missing required properties like
name,url, oreventwill cause errors. - Invalid or expired API credentials will result in authentication failures.
- Incorrect event names may lead to webhook creation but no triggering on events.
- Missing required properties like
Error messages:
"Operação "create" não suportada para webhooks": Indicates an unsupported operation; ensure the operation parameter is set to "create".- HTTP 401 Unauthorized: Check API key validity and permissions.
- HTTP 400 Bad Request: Verify all required fields are correctly filled and valid.
Resolution tips:
- Double-check all required input parameters.
- Confirm API credentials are correct and have necessary permissions.
- Validate the event name against Linqer CRM supported events.
Links and References
- Linqer CRM API Documentation (hypothetical link, replace with actual if available)
- n8n Webhook Node Documentation (for general webhook concepts)
