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 allows you to find and retrieve a document by its unique identifier (Document ID) from the h2oGPT Enterprise system. It is useful when you need to fetch detailed information about a specific document stored in the system, such as metadata, content, or other attributes associated with that document.

Typical use cases include:

  • Retrieving a document's details for display or processing in a workflow.
  • Accessing document metadata for auditing or reporting.
  • Using the document data as input for further automation or AI processing.

For example, if you have a document ID from a previous step or external source, you can use this node to get the full document record to use downstream in your automation.

Properties

Name Meaning
Document ID The unique identifier of the document to return. This is a required string input specifying which document to fetch.

Output

The node outputs the JSON response from the API call that returns the document details corresponding to the provided Document ID. The output typically includes all available information about the document, such as its metadata, content references, status, and other relevant fields.

If the document contains binary data (e.g., files or attachments), the node may also provide binary output representing the document's file content or related binary assets.

Dependencies

  • Requires an API key credential for authentication with the h2oGPT Enterprise API.
  • The node makes HTTP GET requests to the endpoint /documents/{document_id} on the configured base URL.
  • Ensure the API credentials and base URL are correctly set up in n8n to allow successful communication.

Troubleshooting

  • Invalid Document ID: If the provided Document ID does not exist or is incorrect, the API will likely return a 404 error. Verify the ID is correct.
  • Authentication Errors: Missing or invalid API credentials will cause authentication failures. Check that the API key credential is properly configured.
  • Timeouts: Large documents or network issues might cause timeouts. Adjust timeout settings if available or check network connectivity.
  • Permission Denied: If the user associated with the API key lacks permission to access the document, the API will return an authorization error. Ensure proper permissions are granted.

Links and References


This summary focuses specifically on the "Finds a Document by ID" operation under the "Document" resource as requested.

Discussion