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 you to set a user-specific configuration item in the system. It is useful for managing personalized settings or preferences tied to individual users, such as feature toggles, UI preferences, or custom parameters that affect user experience or behavior within an application.

Typical use cases include:

  • Updating a user's preference setting (e.g., theme color, notification settings).
  • Storing user-specific flags or options that control access or features.
  • Managing configuration keys that influence how the system behaves for a particular user.

For example, you might set a configuration key "dashboard_layout" with a value representing the user's preferred dashboard arrangement.

Properties

Name Meaning
User ID The unique identifier of the user for whom the configuration item will be set.
Key Name The key of the configuration item to set (e.g., "theme", "notifications_enabled").
String Value The string value to assign to the configuration key for the user.
Additional Options Optional additional parameters; currently supports:
- Value Type: type of the value (e.g., string, number)

Output

The output JSON contains the response from the API after setting the user configuration item. This typically includes confirmation of the update and may echo back the updated configuration details.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential configured in n8n to authenticate requests to the backend service.
  • The base URL for API requests is derived from the credential's URL, appended with /api/v1.
  • The node sends HTTP PUT requests to the endpoint /users/{user_id}/configurations/{key_name} with the configuration data in the request body.

Troubleshooting

  • Invalid User ID: If the user ID does not exist or is incorrect, the API will likely return an error indicating the user was not found. Verify the user ID is correct.
  • Missing Required Fields: Ensure all required fields (user_id, key_name, string_value) are provided; otherwise, the request will fail.
  • Permission Issues: The API key used must have sufficient permissions to modify user configurations. Lack of permission will result in authorization errors.
  • Value Type Mismatch: If the value_type specified in additional options does not match the actual value format, the API may reject the request. Use appropriate types.
  • Network or Endpoint Errors: Check connectivity and ensure the base URL is correctly configured in credentials.

Links and References

  • No direct external links available from the source code.
  • Refer to your platform's API documentation for detailed information on user configuration management endpoints.

Discussion