Sleak.chat icon

Sleak.chat

Sleak.chat RAG completions API

Actions2

  • Send Message Actions
  • Create Conversation Actions

Overview

This node integrates with the Sleak.chat API to create new conversations within a specified chatbot. It is useful when you want to programmatically start a conversation context in Sleak.chat, for example, to organize messages or interactions under a named conversation associated with a particular chatbot.

Practical scenarios include:

  • Automating the creation of conversation threads for customer support chats.
  • Initializing new chat sessions for users interacting with a chatbot.
  • Structuring conversations by name for easier tracking and retrieval.

Properties

Name Meaning
Chatbot ID The unique identifier of the chatbot under which the conversation will be created.
Name The name to assign to the new conversation, helping to identify or categorize it.

Output

The node outputs JSON data representing the response from the Sleak.chat API after creating the conversation. This typically includes details about the newly created conversation such as its ID, name, associated chatbot ID, timestamps, and other metadata returned by the API.

No binary data output is involved.

Dependencies

  • Requires an API key credential for authenticating requests to the Sleak.chat API.
  • The base URL for API requests is https://api.v1.sleak.chat/api.
  • Proper configuration of the API authentication credential in n8n is necessary.

Troubleshooting

  • Missing or invalid Chatbot ID: Ensure that the Chatbot ID provided is correct and corresponds to an existing chatbot in Sleak.chat.
  • API authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
  • Network or connectivity issues: Confirm that the n8n instance can reach the Sleak.chat API endpoint.
  • Invalid or missing 'Name' property: The conversation name is required; ensure it is provided and not empty.

Common error messages will likely relate to HTTP 4xx or 5xx responses indicating authentication failure, invalid parameters, or server errors. Checking the exact API response message will help diagnose the issue.

Links and References

Discussion