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 create an agent key within the system. Agent keys are typically used for authentication or integration purposes, enabling agents or tools to interact securely with the platform. This operation is beneficial when you need to programmatically generate new keys for agents that require access to specific services or APIs.

Practical examples include:

  • Automating the creation of API keys for new agents in a deployment pipeline.
  • Managing agent credentials dynamically based on user or system requirements.
  • Integrating third-party tools that require unique keys for authentication.

Properties

Name Meaning
Name The name identifier for the agent key being created.
Type The type/category of the agent key.
Value The actual value or secret string of the agent key.
Additional Options Optional additional parameters; currently supports: Description - a textual description of the agent key.

Output

The output will contain the JSON response from the API after creating the agent key. This typically includes details about the newly created key such as its ID, name, type, value (or masked value), and any associated metadata like description. The exact structure depends on the API's response but generally confirms successful creation and provides the key details.

If the node supports binary data output, it would be related to any files or certificates associated with the key, but this operation primarily deals with JSON data.

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 configuration.
  • The node sends HTTP POST requests to the /agents/keys endpoint to create the agent key.

Troubleshooting

  • Missing Required Fields: Ensure that "Name", "Type", and "Value" fields are provided; these are mandatory.
  • Authentication Errors: Verify that the API key credential is correctly set up and has permissions to create agent keys.
  • API Endpoint Issues: Confirm that the base URL is correct and the server is reachable.
  • Duplicate Key Names: If the API rejects duplicate names, use unique names for each key.
  • Invalid Type or Value Format: Check that the "Type" and "Value" conform to expected formats defined by the API.

Links and References

  • Refer to your platform's API documentation for the /agents/keys endpoint for detailed information on request and response formats.
  • Consult the n8n documentation on how to configure API key credentials and use HTTP request nodes if needed.

Discussion