BeeAI

Overview

The node integrates with the BeeAI API to manage conversations, including ending an ongoing conversation. The "End Conversation" operation specifically allows users to terminate a conversation by providing its unique identifier. This is useful in scenarios where a conversation session needs to be closed programmatically, such as after completing a customer support interaction or when cleaning up inactive sessions.

Practical examples:

• Automatically ending a chatbot conversation once the user query has been resolved.
• Closing a conversation session before starting a new one to avoid overlapping contexts.

Properties

Output

The node outputs JSON data representing the result of the "End Conversation" API call. Typically, this will include confirmation that the conversation was successfully ended or details about the terminated conversation. The exact structure depends on the BeeAI API response but generally includes status and metadata about the conversation.

No binary data output is indicated for this operation.

Dependencies

• Requires an API key credential for authenticating with the BeeAI API.
• The node communicates with the BeeAI API endpoint at https://api.bee.computer.
• Proper configuration of the API key credential within n8n is necessary for successful requests.

Troubleshooting

• Missing or invalid Conversation ID: Ensure the Conversation ID property is provided and correctly references an existing conversation.
• Authentication errors: Verify that the API key credential is set up correctly and has sufficient permissions.
• API connectivity issues: Check network access to https://api.bee.computer and confirm no firewall or proxy blocks.
• Unexpected API responses: Review the API documentation for any changes or additional required parameters.

Links and References

• BeeAI API Documentation (assumed base URL; consult official docs for detailed endpoints)
• n8n documentation on API credentials