Linqer CRM

Overview

The "Buscar por ID" operation for the "Contatos" (Contacts) resource in the Linqer CRM node allows users to retrieve detailed information about a specific contact by its unique ID. This operation is useful when you need to fetch up-to-date data on a particular contact, such as their name, email, phone numbers, address, and other relevant details stored in the CRM.

Practical examples include:

• Fetching contact details to personalize communications or marketing campaigns.
• Retrieving contact information before updating records or linking contacts to other CRM entities.
• Integrating with external systems that require contact data synchronization based on contact IDs.

Properties

Output

The output of this operation is a JSON object representing the contact's data as returned by the Linqer CRM API. It typically includes fields such as:

• name: Contact's full name.
• email: Contact's email address.
• mainPhone: Primary phone number.
• secondaryPhone: Secondary phone number.
• type: Type/category of the contact.
• document and documentType: Identification documents.
• address: Physical address.
• industry: Industry sector.
• website: Website URL.
• notes: Additional notes about the contact.
• active: Status indicating if the contact is active.
• tags: Array of tags associated with the contact.
• socialMedia: Social media profiles linked to the contact.

The exact structure depends on the CRM's API response but will be a single JSON object with these or similar properties.

Dependencies

• Requires an API key credential for authenticating requests to the Linqer CRM API.
• The node uses HTTP requests to the Linqer CRM REST API endpoints.
• Proper configuration of the API base URL and authentication credentials within n8n is necessary.

Troubleshooting

• Common issues:

  • Invalid or missing contact ID will result in errors or empty responses.
  • Authentication failures due to incorrect or expired API keys.
  • Network connectivity problems preventing access to the Linqer CRM API.

• Error messages:

  • "Operation 'get' not supported for contacts": Indicates an unsupported operation was requested; ensure the operation parameter is correctly set to "get".
  • HTTP 404 Not Found: The specified contact ID does not exist.
  • HTTP 401 Unauthorized: Authentication failed; verify API credentials.

• Resolutions:

  • Double-check the contact ID input for correctness.
  • Verify API credentials and permissions.
  • Ensure the Linqer CRM API service is reachable from your environment.

Links and References

• Linqer CRM API Documentation (general reference): Linqer CRM API (Note: link is illustrative, replace with actual if available)