Actions20
Overview
This node integrates with the Linq API to manage chat messages within chats. Specifically, for the Chat Message - Get Many operation, it retrieves multiple chat messages associated with a specified chat ID. This is useful when you want to fetch the conversation history or batch process messages from a particular chat.
Common scenarios include:
- Displaying all messages in a chat for analysis or reporting.
- Exporting chat message data for backup or migration.
- Triggering workflows based on recent messages in a chat.
Example: You have a chat identified by its ID and want to retrieve all messages exchanged in that chat to analyze customer support interactions.
Properties
| Name | Meaning |
|---|---|
| Chat ID | The unique identifier of the chat whose messages you want to retrieve. |
Output
The output is an array of JSON objects representing chat messages retrieved from the Linq API. Each object corresponds to a single chat message and contains fields as returned by the API, typically including message text, sender info, timestamps, message ID, and possibly reactions or metadata.
No binary data is output by this operation.
Dependencies
- Requires an API authentication token credential for the Linq API (referred generically as "an API key credential").
- The node makes HTTP requests to the Linq API endpoints.
- Proper configuration of the Linq API credentials in n8n is necessary.
Troubleshooting
- Rate Limit Exceeded: If the node throws an error indicating rate limit exceeded, 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 result in an error or empty results. Verify the chat ID is correct.
- Authentication Errors: Ensure the API token credential is valid and has sufficient permissions.
- Network Issues: Connectivity problems can cause request failures; verify network access to the Linq API endpoint.
Links and References
- Linq API Documentation (generic placeholder, replace with actual if available)
- n8n Documentation on HTTP Request Node (for understanding underlying request mechanics)