Linqer CRM

Overview

This node integrates with the Linqer CRM API to manage various CRM resources, including Webhooks. Specifically, for the Webhooks resource and the Buscar por ID (get) operation, it retrieves detailed information about a specific webhook by its unique ID.

Common scenarios where this node is beneficial include:

• Fetching configuration details of a particular webhook to verify or audit its settings.
• Automating workflows that depend on webhook metadata from Linqer CRM.
• Integrating webhook data retrieval into larger automation pipelines for CRM event handling.

For example, you might use this node to get the URL, event type, and other properties of a webhook registered in Linqer CRM to ensure it is correctly set up before triggering further actions.

Properties

Output

The node outputs JSON data representing the webhook object retrieved from the Linqer CRM API. The structure typically includes fields such as:

• id: The webhook's unique identifier.
• name: The name assigned to the webhook.
• url: The callback URL configured for the webhook.
• event: The event type that triggers the webhook.
• instanceName: The instance name associated with the webhook.
• timestamp: The timestamp related to the webhook configuration or last update.

The exact fields depend on the Linqer CRM API response but generally provide comprehensive details about the webhook configuration.

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 the Linqer CRM API endpoints, so network connectivity to the API server is necessary.
• Proper configuration of the API URL and authentication credentials within n8n is required.

Troubleshooting

• Common issues:

  • Invalid or missing webhook ID: Ensure the "ID do Webhook" property is correctly set and corresponds to an existing webhook.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
  • Network errors: Check connectivity to the Linqer CRM API endpoint.
  • Unsupported operation error: Confirm that the operation is set to "get" when using the Webhooks resource.

• Error messages:

  • "Operação "get" não suportada para webhooks": This indicates an unsupported operation was requested; ensure the operation parameter is correct.
  • HTTP 404 Not Found: The webhook ID does not exist; verify the ID.
  • HTTP 401 Unauthorized: Authentication failed; check API credentials.

Resolving these usually involves verifying input parameters, credentials, and network access.

Links and References

• Linqer CRM API Documentation (Assumed link, replace with actual if available)
• n8n Documentation on Creating Custom Nodes
• General info on Webhook Concepts

Note: All internal credential names and sensitive identifiers have been generalized per guidelines.