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 under the "Permission" resource retrieves a list of all registered users in the system. It is useful for administrative or management scenarios where you need to view or process user information, such as auditing user accounts, managing permissions, or integrating user data with other systems.

Practical examples include:

  • Fetching all users to synchronize with an external directory.
  • Generating reports on user activity or status.
  • Managing access control by reviewing the list of users.

Properties

Name Meaning
Additional Options Optional parameters to control pagination of the user list:
- Offset Number of users to skip before starting to return results (default 0).
- Limit Maximum number of user results to return (minimum 1, default 50).

Output

The output JSON contains an array of user objects representing the registered users in the system. Each user object typically includes details such as user ID, username, email, roles, and other relevant metadata depending on the API response.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authentication to the H2O GPT API.
  • The base URL for API requests is configured from the credential's URL.
  • The node sends a GET request to the /users endpoint with optional query parameters for offset and limit.

Troubleshooting

  • Empty User List: If no users are returned, verify that the API key has sufficient permissions and that users exist in the system.
  • Invalid Credentials: Authentication errors indicate issues with the provided API key; ensure it is valid and has access rights.
  • Pagination Issues: Incorrect offset or limit values may result in unexpected subsets of users; adjust these parameters accordingly.
  • API Endpoint Errors: Network or server errors can occur; check connectivity and API service status.

Links and References


This summary is based on static analysis of the node's configuration and bundled source code related to the "Permission" resource and "list_users" operation.

Discussion