Linqer CRM icon

Linqer CRM

Integração com a API do CRM Linqer

Actions32

Overview

The node integrates with the Linqer CRM API to manage various CRM resources, including custom fields. Specifically, for the "Campos Personalizados" (Custom Fields) resource and the "Buscar por ID" (Get by ID) operation, the node retrieves detailed information about a specific custom field by its unique identifier. This is useful when you need to fetch metadata or configuration details of a particular custom field within your CRM system.

Practical scenarios include:

  • Automating workflows that require validation or processing based on custom field definitions.
  • Synchronizing custom field data between Linqer CRM and other systems.
  • Dynamically adjusting forms or UI elements based on custom field properties fetched from the CRM.

Properties

Name Meaning
ID do Campo The unique identifier (ID) of the custom field to retrieve.

Output

The output is a JSON object representing the custom field's details as returned by the Linqer CRM API. This typically includes properties such as the field's name, type, whether it is required, locked, or a system field, among others.

Example structure (fields may vary):

{
  "id": "string",
  "name": "string",
  "type": "string",
  "required": true,
  "locked": false,
  "isSystem": false,
  ...
}

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 uses HTTP requests with JSON payloads to communicate with the Linqer CRM REST endpoints.
  • Proper configuration of the API URL and authentication credentials in n8n is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing custom field ID will cause the API to return an error.
    • Authentication failures due to incorrect or expired API keys.
    • Network connectivity problems preventing access to the Linqer CRM API.

  • Error messages:

    • "Operação "get" não suportada para campos personalizados": Indicates an unsupported operation was requested; ensure the operation parameter is correctly set to "get".
    • API errors related to invalid IDs or permissions will be passed through; verify the field ID exists and the API key has sufficient rights.

  • Resolutions:

    • Double-check the "ID do Campo" input value for correctness.
    • Verify API credentials and their permissions.
    • Ensure the Linqer CRM API endpoint is reachable from the n8n environment.

Links and References

Discussion