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 prompt template reference associated with a specific collection in the system. It allows users to change which prompt template is linked to a given collection by specifying the collection's unique identifier and the new prompt template's ID. This is useful when you want to modify or improve the prompts used for generating responses or interactions related to that collection.

Common scenarios:

  • Updating the prompt template of a collection to refine AI-generated outputs.
  • Switching between different prompt templates for different use cases or contexts within the same collection.
  • Managing prompt templates dynamically as part of an automated workflow.

Practical example:
You have a collection of documents related to customer support FAQs, and you want to update the prompt template to a new version that better handles conversational queries. Using this node operation, you specify the collection ID and the new prompt template ID to update the reference accordingly.

Properties

Name Meaning
Collection ID The unique identifier of the collection whose prompt template reference you want to update.
Additional Options Optional parameters; currently supports:
- Prompt Template ID: The ID of the new prompt template to associate with the collection.

Output

The output contains the full HTTP response from the API call that updates the prompt template reference of the collection. The json field will typically include confirmation details or the updated collection data reflecting the new prompt template association.

If the operation is successful, the output confirms the update; otherwise, it may contain error information.

Dependencies

  • Requires an API key credential for authentication to the external service managing collections and prompt templates.
  • The base URL for API requests is derived from the configured credentials.
  • The node sends a PUT request to the endpoint /collections/{collection_id}/prompt_template with the new prompt template ID in the request body.

Troubleshooting

  • Missing or invalid Collection ID: Ensure the Collection ID is provided and correctly references an existing collection.
  • Invalid Prompt Template ID: Verify that the prompt template ID exists and is accessible.
  • Authentication errors: Confirm that the API key credential is valid and has sufficient permissions.
  • Network issues or timeouts: Check network connectivity and consider increasing timeout settings if available.
  • API errors: Review the error message returned in the response for details on what went wrong (e.g., permission denied, resource not found).

Links and References

  • Refer to the API documentation of the service managing collections and prompt templates for detailed information on the endpoint /collections/{collection_id}/prompt_template.
  • Consult your platform's documentation on how to configure API key credentials for authenticated requests.

Discussion