Linq icon

Linq

Interact with Linq API

Actions20

Overview

This node integrates with the Linq API to manage various resources such as chats, chat messages, contacts, phone numbers, and webhook subscriptions. Specifically, for the Contact resource with the Get One operation, it retrieves detailed information about a single contact by its unique ID.

Common scenarios where this node is beneficial include:

  • Fetching detailed contact information for customer support or CRM workflows.
  • Integrating contact data retrieval into automated messaging or notification systems.
  • Synchronizing contact details between Linq and other platforms.

For example, you can use this node to get a contact's full profile (name, email, phone number, company, etc.) by providing their Contact ID, then use that data in subsequent workflow steps like sending personalized messages or updating records elsewhere.

Properties

Name Meaning
Contact ID The unique identifier of the contact to retrieve

Output

The node outputs a JSON object representing the contact's data as returned by the Linq API. This typically includes fields such as:

  • id: Contact's unique ID
  • first_name
  • last_name
  • email
  • phone_number
  • company
  • title
  • location

The exact structure depends on the Linq API response but generally contains all stored contact details.

No binary data output is produced by this operation.

Dependencies

  • Requires an active Linq API integration token credential configured in n8n.
  • Makes HTTP requests to the Linq API endpoints using this token for authentication.
  • Network access to https://api.linqapp.com is necessary.

Troubleshooting

  • Rate limit exceeded error: If the node throws "Rate limit exceeded. Please try again after 10 seconds.", it means too many requests were made in a short time. To resolve, add delays between executions or reduce request frequency.
  • Invalid Contact ID: Providing a non-existent or malformed Contact ID will likely result in an error from the API. Verify the Contact ID before running.
  • Authentication errors: Ensure the Linq API credential is correctly set up and has valid permissions.
  • Network issues: Check connectivity to the Linq API endpoint if requests fail.

Links and References

Discussion