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 allows setting a global configuration item in the system. It is designed for administrators who need to define or update global settings that affect the entire environment. The global configuration items set here can control various aspects of the system's behavior and can be made visible or hidden to users, as well as specify whether user-level settings can override them.

Typical use cases include:

  • Defining system-wide feature flags or toggles.
  • Setting default values for application parameters.
  • Controlling visibility and override permissions of configuration keys.

For example, an admin might set a global configuration key "max_upload_size" with a value "100MB", mark it as not public (hidden from users), and prevent users from overriding it.

Properties

Name Meaning
Key Name The key identifier of the global configuration item to set.
String Value The string value to assign to the global configuration key.
Can Overwrite Boolean flag indicating if user-specific settings are allowed to override this global setting.
Is Public Boolean flag indicating if users can see the value of this global configuration item.
Additional Options Collection of optional parameters:
- Value Type: The data type of the value being set (e.g., string, number).

Output

The node outputs the full response from the API call that sets the global configuration item. This typically includes confirmation of the updated configuration item and its details. The output is structured as JSON containing the server's response.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authentication to the backend service.
  • The node sends HTTP PUT requests to the endpoint /configurations/{key_name} on the configured base URL.
  • The base URL and authentication credentials must be properly configured in n8n for successful operation.

Troubleshooting

  • Common Issues:

    • Missing or invalid API key credential will cause authentication failures.
    • Attempting to set a configuration key without required permissions may result in authorization errors.
    • Providing invalid data types or malformed JSON in additional options may cause request failures.
  • Error Messages:

    • 401 Unauthorized: Check that the API key credential is correctly set and has sufficient permissions.
    • 403 Forbidden: The user does not have admin rights to set global configurations.
    • 400 Bad Request: Verify that all required fields are provided and valid, especially the key name and string value.
  • To resolve errors, ensure correct credentials, proper permissions, and valid input data.

Links and References

  • No direct external links available from the source code.
  • For more information, consult the API documentation of the backend service managing global configurations.

Discussion