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 creates associations between a specified tool and the user's keys within an agent context. It is useful when you want to link or bind certain API keys or credentials that a user possesses to a particular tool, enabling the tool to use those keys for authentication or access purposes.

Typical scenarios include:

  • Associating multiple API keys with a third-party tool to enable seamless integration.
  • Managing which keys a tool can use on behalf of a user.
  • Automating the setup of tool-key relationships in workflows where tools require specific user keys.

For example, if you have a tool that requires access to several user API keys, this operation allows you to create those associations programmatically.

Properties

Name Meaning
Tool The identifier or name of the tool to associate with the user's keys. This is a required string input.
Keys A JSON object representing the keys to be associated with the tool. This must be provided and typically contains key-value pairs or structured data defining the keys.

Output

The output will contain the full HTTP response from the API call that creates the association. The main data will be in the json field of the output, which typically includes details about the created associations such as IDs, status, or confirmation messages.

No binary data output is indicated for this operation.

Dependencies

  • Requires an API key credential for authentication to the external service's API.
  • The base URL for API requests is configured via credentials and environment variables.
  • The node sends a POST request to the /agents/tool_association endpoint with the tool and keys data in the request body.

Troubleshooting

  • Missing Required Fields: Ensure both "Tool" and "Keys" properties are provided; otherwise, the API will reject the request.
  • Invalid Keys Format: The "Keys" property must be valid JSON matching the expected structure by the API. Invalid JSON or incorrect schema may cause errors.
  • Authentication Errors: Verify that the API key credential is correctly configured and has sufficient permissions.
  • API Endpoint Issues: If the API endpoint /agents/tool_association is unreachable or returns errors, check network connectivity and API server status.

Common error messages might include:

  • 400 Bad Request: Usually due to missing or malformed parameters.
  • 401 Unauthorized: Authentication failure due to invalid or missing API key.
  • 403 Forbidden: Insufficient permissions to create associations.
  • 500 Internal Server Error: Server-side issues; retry later or contact support.

Links and References

  • Refer to the external API documentation for the /agents/tool_association endpoint for detailed information on the expected payload and response.
  • Consult your platform's API key management guide to ensure proper credential setup.

Discussion