Actions20
Overview
This node interacts with the Linq API to manage chat messages within the Linq messaging platform. Specifically, the "Chat Message" resource with the "Get One" operation retrieves a single chat message by its unique ID. This is useful when you need to fetch detailed information about a specific message, such as its content, sender, timestamp, or reactions.
Common scenarios include:
- Retrieving a particular message for display or processing in workflows.
- Auditing or logging message details.
- Triggering actions based on the content or metadata of a specific message.
Example: You have a workflow that processes incoming chat messages and needs to fetch full details of a selected message by its ID to analyze or forward it.
Properties
| Name | Meaning |
|---|---|
| Chat Message ID | The unique identifier of the chat message to retrieve. |
Output
The output contains a JSON object representing the retrieved chat message. This typically includes all available data fields returned by the Linq API for that message, such as:
- Message text content
- Sender information
- Timestamp
- Message status
- Any associated reactions or metadata
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Linq API.
- The node makes HTTP GET requests to the Linq API endpoint for chat messages.
- Proper configuration of the API key credential in n8n is necessary.
Troubleshooting
- Rate Limit Errors: If the node throws a "Rate limit exceeded" error, it means too many requests were made in a short time. Wait at least 10 seconds before retrying.
- Invalid Chat Message ID: Providing a non-existent or malformed chat message ID will likely result in an error from the API. Verify the ID is correct.
- Authentication Issues: Ensure the API key credential is valid and has the required permissions.
- Network Issues: Connectivity problems can cause request failures; verify network access to the Linq API.
Links and References
- Linq API Documentation (general reference for endpoints and data structures)
- n8n documentation on HTTP Request Node for understanding underlying request mechanics