Linq icon

Linq

Interact with Linq API
Join our community

Actions20

Overview

This node integrates with the Linq API to manage chat-related data and operations. Specifically, for the Chat - Get One operation, it retrieves detailed information about a single chat by its unique ID. This is useful when you want to fetch the full details of a specific chat conversation, such as participants, messages summary, or metadata.

Common scenarios include:

  • Fetching chat details to display in a dashboard or user interface.
  • Retrieving chat information before performing further actions like sending messages or sharing contacts.
  • Integrating chat data into workflows that require context about a particular conversation.

Example: You have a chat ID from a previous step or external source, and you want to get all associated information about that chat to process or analyze it further.

Properties

Name Meaning
Chat ID The unique identifier of the chat to retrieve

Output

The output is a JSON object representing the chat details returned by the Linq API for the specified chat ID. This typically includes information such as chat participants, chat metadata, timestamps, and possibly message summaries depending on the API response structure.

The node does not output binary data for this operation.

Example output structure (simplified):

{
  "id": "string",
  "display_name": "string",
  "phone_numbers": ["string"],
  "created_at": "string",
  "updated_at": "string",
  // other chat-specific fields...
}

Dependencies

  • Requires an active Linq API integration token credential configured in n8n.
  • Makes HTTP requests to the Linq API endpoint https://api.linqapp.com/api/partner/v2/chats/{chatId}.
  • The node expects the API token to be provided via headers for authentication.

Troubleshooting

  • Rate limit exceeded error: If the node throws an error indicating rate limits (HTTP status 429), wait at least 10 seconds before retrying. This is enforced by the Linq API.
  • Invalid Chat ID: Providing an incorrect or non-existent chat ID will likely result in an error or empty response. Verify the chat ID is correct.
  • Authentication errors: Ensure the API token credential is valid and has the necessary permissions.
  • Network issues: Check connectivity to the Linq API endpoint if requests fail.

Links and References

Discussion