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 removes a prompt template reference from an existing chat session identified by its session ID. It is useful when you want to disassociate or clear the prompt template linked to a particular chat session, effectively resetting or removing any custom prompt behavior associated with that session.

Common scenarios:

  • You have assigned a specific prompt template to a chat session but want to revert it back to default or no prompt template.
  • Cleaning up or resetting chat sessions before reusing them for different contexts.
  • Managing chat session configurations dynamically in workflows where prompt templates are conditionally applied.

Practical example:
If you have a chat session with a custom prompt template guiding the AI's responses and later decide to remove this customization, you can use this operation to delete the prompt template reference from that chat session by providing the session ID.

Properties

Name Meaning
Session ID The unique identifier of the chat session from which the prompt template reference will be removed.

Output

The output of this operation typically contains the full HTTP response from the API call that deletes the prompt template reference. This includes status information indicating whether the deletion was successful. The json field will contain the parsed response body, which may be empty or include confirmation details depending on the API implementation.

No binary data is expected from this operation.

Dependencies

  • Requires an active connection to the H2O GPT API endpoint.
  • Requires valid API authentication credentials (an API key or token) configured in n8n.
  • The base URL for the API is derived from the credential configuration.
  • The node sends an HTTP DELETE request to the endpoint /chats/{session_id}/prompt_template.

Troubleshooting

  • Invalid Session ID: If the provided session ID does not exist or is incorrect, the API will likely return a 404 Not Found error. Verify the session ID is correct.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures (e.g., 401 Unauthorized). Ensure the API key/token is correctly set up.
  • Permission Issues: Insufficient permissions to modify the chat session may result in 403 Forbidden errors. Confirm your API user has the necessary rights.
  • Network Issues: Connectivity problems can cause request timeouts or failures. Check network access to the API endpoint.
  • Timeouts: The operation supports a timeout option; if the request takes too long, it may fail. Adjust the timeout setting as needed.

Links and References


This summary is based solely on static analysis of the provided source code and property definitions without runtime execution.

Discussion