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 deletes one or more agent keys identified by their IDs. Agent keys are typically used for authentication or integration purposes within an agent system. This operation is useful when you want to revoke access or clean up unused or compromised keys associated with agents.

Common scenarios:

  • Removing outdated or compromised API keys for security.
  • Cleaning up keys that are no longer needed after a project or integration ends.
  • Managing agent key lifecycle in automated workflows.

Example:
You have several agent keys issued for different tools or users, and you want to delete specific keys by providing their IDs to ensure they can no longer be used.

Properties

Name Meaning
Key IDs IDs of keys to be deleted

The "Key IDs" property expects a string containing one or more key identifiers that specify which agent keys should be deleted.

Output

The output will contain the full HTTP response from the API call that deletes the specified agent keys. The json field will typically include confirmation of deletion or any error messages returned by the server.

No binary data output is expected from this operation.

Dependencies

  • Requires an API key credential for authentication to the H2O GPT API.
  • The base URL for the API is configured via credentials and is used to construct the request endpoint.
  • The node sends a DELETE HTTP request to the /agents/keys/{key_ids} endpoint, where {key_ids} is replaced by the provided key IDs.

Troubleshooting

  • Invalid or missing Key IDs: Ensure that the "Key IDs" input is provided and correctly formatted. Missing or incorrect IDs will cause the API to return an error.
  • Authentication errors: Verify that the API key credential is valid and has sufficient permissions to delete agent keys.
  • Network or timeout issues: Check network connectivity and consider increasing timeout settings if requests fail due to delays.
  • API errors: If the API returns an error, review the message for details such as non-existent keys or insufficient permissions.

Links and References

  • Refer to the H2O GPT API documentation for details on managing agent keys and the DELETE /agents/keys/{key_ids} endpoint.
  • Consult your platform's API key management guidelines for best practices on key lifecycle management.

Discussion