Linqer CRM icon

Linqer CRM

Integração com a API do CRM Linqer

Actions32

Overview

The "Buscar Todos" (Get All) operation for the "Contatos" (Contacts) resource in this Linqer CRM node retrieves a list of contacts from the Linqer CRM system. This operation is useful when you want to fetch all contact records, optionally filtered by an account ID, to integrate or synchronize contact data with other systems or workflows.

Practical examples include:

  • Importing all contacts into another database or CRM.
  • Generating reports or analytics based on all contacts.
  • Synchronizing contacts between Linqer CRM and marketing automation tools.

Properties

Name Meaning
Account ID ID of the account used to filter contacts. (Optional filter parameter for some operations)

Note: For the "Buscar Todos" operation on contacts, the provided bundled code does not explicitly use the Account ID parameter in the API request URL or body. However, it is defined as an input property and may be intended for filtering in some contexts or future enhancements.

Output

The output is a JSON array where each item represents a contact object retrieved from the Linqer CRM API endpoint /v1/contacts/public. Each contact object typically includes fields such as name, email, phone numbers, type, document details, address, industry, website, notes, tags, social media links, and active status.

The node returns these contact objects as JSON data, which can then be used downstream in n8n workflows.

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 the base API URL configured in the credential.
  • The node depends on the Linqer CRM REST API being accessible and responsive.

Troubleshooting

  • Empty results: If no contacts are returned, verify that the account ID filter (if used) is correct and that there are contacts associated with that account.
  • Authentication errors: Ensure the API key credential is valid and has sufficient permissions.
  • API errors: Network issues or API downtime can cause failures; check connectivity and Linqer CRM service status.
  • Unsupported operation error: If the operation or resource is misspelled or unsupported, the node will throw an error indicating the unsupported resource or operation.

Links and References

Discussion