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 "Gets Stats of an Agent Server Directory" under the "Chat" resource retrieves statistical information about a specific directory on an agent server associated with a chat session. It is useful for monitoring and analyzing the contents or usage metrics of directories managed by an agent within a chat session context.

Typical use cases include:

  • Monitoring storage or file usage in agent server directories related to chat sessions.
  • Gathering detailed statistics for troubleshooting or auditing purposes.
  • Integrating directory stats into workflows that manage or analyze chat session data.

For example, you might use this node to get the size, number of files, or other metadata about a directory used by an AI agent during a chat session to optimize resource allocation or debug issues.

Properties

Name Meaning
Session ID The unique identifier of the chat session for which the agent server directory stats are requested. This is required.
Directory Name The name of the directory on the agent server whose statistics are to be retrieved. This is required.
Additional Options Optional parameters to customize the request. Currently supports:
- Detail Level: A numeric value where a higher number returns more detailed stats.

Output

The output JSON contains the statistical data returned from the agent server directory specified by the session ID and directory name. The exact structure depends on the API response but typically includes metrics such as file counts, sizes, timestamps, and possibly other directory metadata.

If binary data were involved (not indicated here), it would represent raw files or similar content, but this operation focuses on stats, so output is JSON-formatted metadata.

Dependencies

  • Requires an API key credential for authentication to the h2oGPT API endpoint.
  • The base URL for the API is configured via credentials.
  • The node sends a GET request to the endpoint /chats/{session_id}/agent_server_directories/{directory_name}/stats.
  • Optional query parameter detail_level can be set to control the verbosity of the returned stats.

Troubleshooting

  • Missing or invalid Session ID or Directory Name: The API will likely return an error if these required parameters are missing or incorrect. Ensure both are provided and valid.
  • Authentication errors: If the API key credential is missing or invalid, requests will fail with authorization errors.
  • Network or connectivity issues: Ensure the API base URL is reachable from your n8n environment.
  • Detail Level too high: Setting an excessively high detail level might cause large responses or timeouts; try lowering the value if performance issues occur.

Links and References


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

Discussion