Overview
This node integrates with the Sleak.chat API to send messages within an existing conversation. It is designed to post a text message to a specified conversation identified by its unique ID. This functionality is useful in scenarios where automated messaging or chatbot interactions need to be programmatically controlled, such as sending notifications, updates, or user queries to a chat system.
Practical examples include:
- Sending customer support responses automatically from a workflow.
- Posting alerts or status updates into a team chat channel.
- Integrating chatbot replies into ongoing conversations.
Properties
| Name | Meaning |
|---|---|
| Conversation ID | The unique identifier of the conversation where the message will be posted. |
| Message | The text content of the message to send to the specified conversation. |
Output
The node outputs JSON data representing the response from the Sleak.chat API after posting the message. This typically includes confirmation details about the sent message, such as message ID, timestamps, or status. The output does not handle binary data.
Dependencies
- Requires an API key credential for authenticating with the Sleak.chat service.
- The node sends HTTP POST requests to the Sleak.chat API endpoint at
https://api.v1.sleak.chat/api/message. - Proper configuration of the API key credential in n8n is necessary for successful operation.
Troubleshooting
Common issues:
- Invalid or missing Conversation ID can cause the API to reject the request.
- Incorrect or expired API authentication token will result in authorization errors.
- Network connectivity problems may prevent reaching the Sleak.chat API endpoint.
Error messages and resolutions:
- 401 Unauthorized: Check that the API key credential is correctly configured and valid.
- 400 Bad Request: Verify that the Conversation ID and Message fields are correctly filled and conform to expected formats.
- 404 Not Found: Ensure the Conversation ID exists and is accessible with the provided credentials.
- Timeouts or network errors: Confirm internet connectivity and that the Sleak.chat API service is operational.
Links and References
- Sleak.chat API Documentation (for detailed API usage and message format)
- n8n documentation on HTTP Request Node (conceptual similarity)