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 all users' collection metadata, sorted by the last update time by default. It is primarily designed for administrative use to retrieve comprehensive metadata about collections across all users in the system. This can be useful for administrators who need to monitor, audit, or manage collections at a global level.

Practical examples include:

  • An admin dashboard displaying all collections with their latest update times.
  • Generating reports on collection usage and status.
  • Auditing collections for compliance or organizational purposes.

Properties

Name Meaning
Offset How many collections to skip before returning results (pagination offset).
Limit Maximum number of collection results to return (minimum 1).
Sort Column The column by which to sort the collections. Options: Archived At, Document Count, Document Size, Expiry Date, Inactivity Interval, Name, Sessions Count, Status, Updated At, Username. Default is "Updated At".
Ascending Boolean flag indicating whether to sort in ascending order (true) or descending order (false). Default is false.

Output

The output JSON contains an array of collection metadata objects representing all users' collections. Each object includes details such as collection identifiers, names, descriptions, timestamps (including last updated), document counts, sizes, statuses, and other relevant metadata fields.

The node does not output binary data; it strictly returns structured JSON metadata about collections.

Dependencies

  • Requires an API key credential for authentication to the external service.
  • The base URL for API requests is configured dynamically from credentials.
  • No additional external dependencies are required beyond proper API access.

Troubleshooting

  • Common Issues:

    • Insufficient permissions: Since this operation is for admin use, non-admin users may receive authorization errors.
    • Invalid or missing API key credential will cause authentication failures.
    • Providing invalid values for pagination or sorting parameters may result in errors or unexpected results.
  • Error Messages:

    • Authorization errors typically indicate lack of admin privileges.
    • Validation errors may occur if limit is less than 1 or if unsupported sort_column values are provided.
    • Network or timeout errors may happen if the API endpoint is unreachable or slow.
  • Resolutions:

    • Ensure the API key has admin-level permissions.
    • Validate input parameters before execution.
    • Check network connectivity and API server status.

Links and References

  • Refer to the external API documentation for detailed information on collection metadata fields and sorting options.
  • Consult your platform's admin guide for managing API keys and permissions related to collections.

Discussion