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 resets the prompt settings for a specified collection within the h2oGPTe system. The h2oGPTe platform is an AI-powered search assistant designed to help internal teams answer questions by leveraging large volumes of documents, websites, and workplace content. Resetting prompt settings can be useful when you want to clear any custom prompt configurations applied to a collection and revert it to default prompt behavior.

Common scenarios:

  • When a collection's prompt settings have been customized but need to be cleared to troubleshoot or start fresh.
  • To remove any prompt templates or modifications that affect how queries are processed against the collection.
  • Preparing a collection for new prompt settings by first resetting existing ones.

Practical example:
You manage a document collection used by your support team. After experimenting with different prompt templates, you decide to reset the prompt settings to default before applying a new template. This node operation allows you to do that by specifying the collection ID.

Properties

Name Meaning
Collection ID The unique identifier (ID) of the collection whose prompt settings will be reset. This is a required string input.

Output

The output of this operation is the full HTTP response from the API call that deletes the prompt settings for the given collection. The json field in the output contains the response data from the server after successfully resetting the prompt settings.

If the operation is successful, the response typically confirms that the prompt settings have been reset. No binary data is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the h2oGPTe API.
  • The node sends an HTTP DELETE request to the endpoint /collections/{collection_id}/prompt_settings.
  • The base URL for the API is configured via credentials and must be set correctly.
  • Proper permissions on the collection are necessary to perform this operation.

Troubleshooting

  • Invalid Collection ID: If the provided collection ID does not exist or is incorrect, the API will return an error indicating the collection was not found. Verify the collection ID.
  • Authentication Errors: Missing or invalid API key credentials will cause authentication failures. Ensure valid credentials are configured.
  • Permission Denied: If the user associated with the API key lacks permission to modify the collection, the operation will fail. Check user permissions.
  • Network Issues: Connectivity problems may prevent the API call from succeeding. Confirm network access to the API endpoint.
  • Timeouts: Large collections or slow responses might cause timeouts. Adjust timeout settings if available.

Links and References


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

Discussion