Actions20
Overview
This node integrates with the Linq API to manage chat messages within chats. Specifically, for the Chat Message - Edit operation, it allows users to update the text content of an existing chat message by specifying its unique ID and the new message text.
Common scenarios where this node is beneficial include:
- Correcting typos or errors in previously sent chat messages.
- Updating information in a chat message after additional context is available.
- Moderating or managing chat content programmatically.
For example, if a user wants to change the text of a specific chat message identified by its ID, they can use this node to send the updated text to the Linq platform, which will then reflect the changes in the chat.
Properties
| Name | Meaning |
|---|---|
| Chat Message ID | The unique identifier of the chat message to edit. |
| Message Text | The new text content that will replace the existing message text in the specified chat message. |
Output
The node outputs the JSON response returned by the Linq API after editing the chat message. This typically includes details about the updated chat message such as its ID, updated text, timestamps, and possibly metadata related to the message.
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 POST requests to the Linq API endpoint for editing chat messages:
https://api.linqapp.com/api/partner/v2/chat_messages/{chatMessageId}/edit - The request includes the API token in the header
X-LINQ-INTEGRATION-TOKEN. - The node expects the environment to have internet access to reach the Linq API.
Troubleshooting
- Rate Limit Exceeded: If the node throws an error indicating "Rate limit exceeded. Please try again after 10 seconds.", it means too many requests were made in a short period. To resolve, implement retry logic with delays or reduce request frequency.
- Invalid Chat Message ID: Providing an incorrect or non-existent chat message ID will likely result in an error from the API. Verify the ID before using it.
- Empty or Missing Message Text: Sending an empty string or missing the new message text may cause the API to reject the request. Ensure the "Message Text" property is properly set.
- Authentication Errors: If the API key credential is invalid or missing, the node will fail to authenticate. Confirm that the API key is correctly configured in n8n credentials.
Links and References
- Linq API Documentation (general reference; actual URL may vary)
- n8n HTTP Request Node Documentation (for understanding how HTTP requests are made)
- Handling Rate Limits (if available, for best practices on rate limiting)