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

This node operation updates the collection reference of an existing chat session. It allows you to change which collection a particular chat session is associated with by specifying the chat session ID and the new collection ID. This is useful in scenarios where chat sessions need to be re-categorized or linked to different collections of documents or data sources, enabling more relevant context or information retrieval during the chat.

Practical examples:

  • Reassigning a chat session from a general knowledge base collection to a specialized product documentation collection.
  • Updating the collection reference when the underlying data grouping changes or is reorganized.
  • Managing chat sessions dynamically in workflows that involve multiple document collections.

Properties

Name Meaning
Session ID The unique identifier of the chat session to update. This is required to specify which chat session's collection reference will be changed.
Collection ID The unique identifier of the new collection to associate with the chat session. This updates the chat session's collection reference to this new collection.

Output

The output of this operation typically includes the full HTTP response from the API call that updates the chat session's collection reference. The json output field contains the updated chat session details reflecting the new collection association.

If the operation is successful, the output JSON will confirm the update, usually including identifiers and metadata of the chat session and its new collection reference.

No binary data output is expected for this operation.

Dependencies

  • Requires an API key credential for authentication to the external service.
  • The node makes an HTTP PUT request to the endpoint /chats/{session_id}/collection with the new collection ID in the request body.
  • The base URL and headers are configured via credentials and node settings.

Troubleshooting

  • Invalid Session ID: If the provided session ID does not exist, the API will return an error indicating the chat session was not found. Verify the session ID is correct.
  • Invalid Collection ID: If the collection ID is invalid or does not exist, the update will fail. Ensure the collection ID is valid and accessible.
  • Authentication Errors: Missing or incorrect API key credentials will cause authorization failures. Confirm that the API key is correctly configured.
  • Network Issues: Connectivity problems can cause request failures. Check network access and endpoint availability.
  • Permission Denied: The user associated with the API key must have permission to modify the chat session and access the target collection.

Links and References

  • Refer to the API documentation of the chat service for details on updating chat session collection references.
  • Consult n8n documentation on configuring API credentials and HTTP request nodes for integration setup.

Discussion