Linqer CRM icon

Linqer CRM

Integração com a API do CRM Linqer

Actions32

Overview

The node integrates with the Linqer CRM API to update contact information. It allows users to modify existing contacts by specifying their unique ID and updating various fields such as name, email, phone numbers, document details, address, industry, website, notes, tags, active status, and social media links.

This node is beneficial in scenarios where you need to keep your CRM contacts up-to-date automatically from other systems or workflows, such as syncing updated customer data from a form submission, enriching contact profiles with additional information, or correcting contact details programmatically.

Practical example:
You receive updated contact information from a web form or another system and want to reflect those changes in your Linqer CRM without manual entry. Using this node, you can automate the update process by providing the contact ID and new values for the desired fields.

Properties

Name Meaning
Nome The contact's full name (required).
Email The contact's email address.
Telefone Principal The primary phone number of the contact.
Telefone Secundário The secondary phone number of the contact.
Tipo The type of contact: "Individual" or "Empresa" (Company).
Documento The contact's document number (CPF or CNPJ).
Tipo de Documento The type of document: "CPF" or "CNPJ".
Endereço The contact's address.
Setor The industry sector the contact belongs to.
Website The contact's website URL.
Notas Notes about the contact (multi-line text).
Tags Comma-separated tags associated with the contact.
Ativo Boolean indicating if the contact is active.
Redes Sociais Social media links including Facebook, Instagram, LinkedIn, and Twitter.
ID do Contato The unique identifier of the contact to update (required).

Output

The node outputs JSON data representing the updated contact object returned by the Linqer CRM API after a successful update operation. This JSON includes all the contact fields that were updated or present in the contact record.

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 methods (PUT) to communicate with the endpoint ${apiUrl}/v1/contacts/public/{contactId}.
  • The apiUrl is configured in the credential settings.
  • Proper network access to the Linqer CRM API endpoints is necessary.

Troubleshooting

  • Common issues:

    • Missing or invalid contact ID will cause the update to fail.
    • Providing empty strings for optional fields results in those fields being omitted from the update payload.
    • Incorrect API credentials or expired tokens will lead to authentication errors.
    • Network connectivity problems may cause request timeouts or failures.

  • Error messages:

    • "Operation 'update' not supported for contacts": Indicates an unsupported operation was requested; ensure the operation parameter is set correctly.
    • Authentication errors typically indicate invalid or missing API credentials.
    • Validation errors from the API may occur if required fields are missing or field formats are incorrect (e.g., invalid email or document format).

  • Resolutions:

    • Verify the contact ID is correct and exists in the CRM.
    • Ensure all required fields are provided.
    • Check and update API credentials in n8n.
    • Confirm network connectivity and API endpoint accessibility.

Links and References

Discussion