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

The node provides an interface to update the metadata of a document within a document management or knowledge system. This operation is useful when you need to completely replace or recreate the metadata associated with a specific document, such as updating tags, descriptions, custom fields, or other metadata attributes.

Typical use cases include:

  • Correcting or enriching document metadata after initial ingestion.
  • Synchronizing metadata from external systems.
  • Automating metadata updates in workflows that manage document lifecycle or categorization.

For example, if you have a document representing a research paper and want to update its metadata to include new keywords or change its classification, this node operation allows you to do so by specifying the document ID and providing the new metadata.

Properties

Name Meaning
Document ID The unique identifier of the document whose metadata you want to update. This is required.

Output

The output of this operation will be the full response from the API call that updates the document metadata. Typically, this includes confirmation of the update and the updated metadata object for the document.

The json output field will contain the updated metadata details of the document after the operation completes successfully.

There is no indication that this operation outputs binary data.

Dependencies

  • Requires an API key credential for authentication to the backend service managing documents.
  • The node sends HTTP PUT requests to an endpoint structured as /documents/{document_id}/metadata.
  • The base URL and headers are configured via credentials and node settings.

Troubleshooting

  • Missing Document ID: The operation requires a valid Document ID. Ensure this property is set; otherwise, the request will fail.
  • Invalid Metadata Format: If the metadata payload is malformed or missing required fields, the API may reject the update. Validate the metadata JSON before sending.
  • Authentication Errors: Ensure the API key credential is correctly configured and has permissions to update document metadata.
  • Network or Timeout Issues: Large metadata or slow network can cause timeouts. Adjust timeout settings if available.
  • API Endpoint Changes: If the backend API changes the endpoint or request format, the node configuration must be updated accordingly.

Links and References

  • Refer to your document management system's API documentation for details on the metadata structure and update semantics.
  • Consult n8n documentation on how to configure API key credentials and HTTP request nodes for similar operations.

Discussion