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 "Adds Plain Text to a Collection" allows users to ingest raw plain text content into a specified document collection within the system. It is useful for scenarios where you have textual data that you want to organize, index, and make searchable or analyzable as part of a larger document management or AI-powered knowledge base system.

Typical use cases include:

  • Adding notes, reports, or articles directly as text documents into a collection.
  • Quickly ingesting textual data without needing to upload files.
  • Enriching collections with additional context or documentation in plain text form.

For example, a user might input meeting minutes or research summaries as plain text to be stored and later queried or summarized by AI models integrated with the platform.

Properties

Name Meaning
Collection ID String ID of the collection to add the ingested documents into
File Name The file name string to assign to the new document created from the plain text
Text The actual plain text content to ingest into the collection
Additional Options Optional settings including:
- Gen Doc Summaries: Boolean to auto-generate document summaries using an LLM
- Gen Doc Questions: Boolean to auto-generate sample questions for the document using an LLM
- Timeout: Number specifying request timeout in seconds
- Metadata: JSON-encoded string containing metadata for the document

Output

The output will contain the response from the API after adding the plain text document to the collection. This typically includes details about the newly created document such as its unique identifier, status, and any generated summaries or questions if those options were enabled.

The json output field will hold this structured response data. There is no binary data output for this operation.

Dependencies

  • Requires an API key credential for authentication to the backend service.
  • The node sends a POST request to the /ingest/plain_text endpoint with appropriate headers (Content-Type: text/plain).
  • The base URL and authentication are configured via credentials in n8n.

Troubleshooting

  • Missing Required Fields: Ensure Collection ID, File Name, and Text are provided; these are mandatory.
  • Timeouts: If the ingestion takes too long, increase the Timeout option or check network connectivity.
  • Invalid Metadata: The Metadata field must be a valid JSON string; invalid JSON will cause errors.
  • Authentication Errors: Verify that the API key credential is correctly set up and has permissions to ingest documents.
  • API Endpoint Errors: Check that the backend service URL is correct and accessible.

Links and References

  • No direct external links available from the source code.
  • Refer to the platform's API documentation for /ingest/plain_text for more details on request/response formats and capabilities.

Discussion