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 fetches meta information about a specific chat message within a chat system. It allows users to retrieve various types of metadata related to a chat message, such as self-reflection data, usage statistics, raw prompt data, and other internal metadata types. This is useful for analyzing or auditing chat interactions, understanding message context, or gathering insights on how messages are processed by the system.

Practical examples include:

  • Retrieving self-reflection metadata to understand how an AI model evaluated its own response.
  • Fetching usage statistics to monitor resource consumption or performance metrics related to a particular message.
  • Accessing raw prompt data for debugging or auditing purposes.

Properties

Name Meaning
Message ID The unique identifier of the chat message whose metadata is to be fetched.
Additional Options Collection of optional parameters:
- Info Type The type of metadata to fetch. Options include:
- Hyde1: A specific internal metadata type.
- Llm Only: Metadata related only to the language model.
- Prompt Raw: The raw prompt data associated with the message.
- Self Reflection: Metadata containing self-reflection information from the model.
- Usage Stats: Statistics about usage related to the message.

Output

The output JSON contains the requested metadata information for the specified chat message. The exact structure depends on the selected "Info Type" but generally includes detailed metadata fields relevant to the message's processing, reflection, or usage statistics.

If binary data were involved (not indicated here), it would typically represent files or media associated with the message, but this operation focuses on JSON metadata.

Dependencies

  • Requires an API key credential for authentication to the backend service.
  • The node sends an HTTP GET request to the endpoint /messages/{message_id}/meta with query parameters specifying the metadata type.
  • The base URL and headers are configured via credentials and node settings.

Troubleshooting

  • Missing or invalid Message ID: Ensure that the "Message ID" property is provided and corresponds to an existing message in the system.
  • Invalid Info Type: Selecting an unsupported info type may result in errors or empty responses. Use one of the predefined options.
  • Authentication errors: Verify that the API key credential is correctly configured and has permissions to access message metadata.
  • Network issues: Check connectivity to the API endpoint and ensure the base URL is correct.
  • Timeouts: Large metadata requests might time out; consider limiting the scope or increasing timeout settings if available.

Links and References

  • No direct external links provided in the source code.
  • For more details, consult the API documentation of the chat system or platform providing the metadata endpoints.

Discussion