h2oGPTe icon

h2oGPTe

h2oGPTe is an AI-powered search assistant for your internal teams to answer questions gleaned from large volumes of documents, websites and workplace content.

Actions198

Overview

The "Creates Chat Session" operation in the Chat resource allows users to create a new chat session. This session can be associated with a specific collection of documents or operate as a generic large language model (LLM) chat if no collection is specified. This node is useful for initiating interactive AI-powered conversations that leverage document collections for context-aware responses.

Common scenarios include:

  • Starting a new chat session linked to a particular knowledge base or document collection.
  • Creating a generic chat session for general-purpose AI interactions without specific document context.
  • Integrating conversational AI into workflows where dynamic chat sessions are needed.

Example use case:

  • A support team wants to start a chat session that references a specific product documentation collection to answer customer queries more effectively.

Properties

Name Meaning
Additional Options Collection of optional parameters; currently supports:
- Collection ID The unique identifier of the collection to associate with the chat session (optional).

The "Additional Options" property is a collection allowing the user to specify extra parameters. For this operation, it includes only one option:

  • Collection ID: If provided, the chat session will be created with this collection as context; otherwise, the session will be generic.

Output

The output of this operation is the full response from the API call to create a chat session. The main data is available in the json field of the output and typically contains details about the newly created chat session, such as its unique session ID and metadata.

If the API supports binary data for this operation, it would be included accordingly, but based on the static analysis, this operation returns JSON data representing the chat session.

Dependencies

  • Requires an API key credential for authentication to the H2O GPT API endpoint.
  • The base URL for API requests is configured via credentials and environment variables.
  • The node sends HTTP POST requests to the /chats endpoint, optionally including a collection_id query parameter.

Troubleshooting

  • Missing or invalid API key: Ensure the API key credential is correctly configured and valid.
  • Invalid collection ID: If specifying a collection ID, verify that it exists and the user has access rights.
  • Network issues: Check connectivity to the API endpoint.
  • Timeouts: Large or complex requests might time out; consider adjusting timeout settings if available.
  • API errors: Review error messages returned by the API for guidance on required parameters or permission issues.

Links and References

  • H2O GPT API Documentation (general reference for API endpoints)
  • n8n documentation on creating custom nodes and using HTTP request nodes for API integration

Discussion