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 removes a specified tag from a given document within the system. It is useful in scenarios where documents are tagged for categorization, filtering, or metadata purposes, and you need to dynamically update or clean up these tags by removing one or more tags from specific documents.

For example, if a document was mistakenly tagged with "urgent" but no longer requires that label, this operation can remove the "urgent" tag from that document. This helps maintain accurate tagging and organization of documents.

Properties

Name Meaning
Document ID The unique identifier of the document from which the tag will be removed.
Tag Name The name of the tag to be removed from the document.

Output

The output contains the JSON response from the API after attempting to remove the tag from the document. This typically includes confirmation of success or details about the removal operation. The exact structure depends on the API's response but generally confirms whether the tag was successfully removed.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authentication to the external service.
  • The node sends an HTTP DELETE request to the endpoint /documents/{document_id}/tags/{tag_name}.
  • The base URL and headers are configured via credentials and node settings.

Troubleshooting

  • Common Issues:

    • Invalid or missing Document ID or Tag Name parameters will cause the operation to fail.
    • Attempting to remove a tag that does not exist on the document may result in an error or no change.
    • Insufficient permissions or invalid API key credentials can lead to authorization errors.
  • Error Messages:

    • 404 Not Found: The document or tag specified does not exist. Verify the IDs and tag names.
    • 401 Unauthorized: Authentication failed due to invalid or missing API key. Check credentials.
    • 400 Bad Request: Parameters are missing or malformed. Ensure Document ID and Tag Name are correctly provided.

Links and References

  • Refer to the API documentation of the document management system for detailed information on tag management endpoints.
  • Consult your platform’s credential setup guide to configure the required API key authentication.

Discussion