Qontext icon

Qontext

Use the Qontext API

Actions5

Overview

The node integrates with the Qontext API to ingest unstructured text data into a specified context vault within a workspace. This operation is useful for scenarios where users want to add raw textual information into a knowledge base or context vault for later retrieval, analysis, or enrichment.

Practical examples include:

  • Uploading meeting notes or transcripts into a knowledge graph.
  • Adding customer feedback or support tickets as unstructured text to a centralized context vault.
  • Feeding raw documents or articles into an AI-powered knowledge system for further processing.

Properties

Name Meaning
Workspace ID The identifier of the workspace that contains the target context vault.
Context Vault ID The identifier of the specific vault (knowledge graph) where the unstructured text will be ingested.
Text The actual unstructured text content to be ingested into the vault.

Output

The node outputs JSON data representing the response from the Qontext API after attempting to ingest the provided unstructured text. This typically includes confirmation details such as ingestion status, identifiers of created or updated records, and any metadata returned by the API.

If the node supports binary data output, it would represent related artifacts or files generated during ingestion, but based on the provided code and properties, the primary output is JSON structured data confirming the ingestion result.

Dependencies

  • Requires an active connection to the Qontext API endpoint at https://api.staging.qontext.ai/v1.
  • Needs an API key credential configured in n8n to authenticate requests (X-API-Key header).
  • The node depends on correct workspace and vault IDs to route the ingestion properly.

Troubleshooting

  • Invalid Workspace or Vault ID: If the provided IDs are incorrect or do not exist, the API may return errors indicating resource not found. Verify IDs before running the node.
  • Authentication Errors: Missing or invalid API key credentials will cause authentication failures. Ensure the API key is correctly set up in n8n credentials.
  • Empty or Malformed Text: Providing empty or improperly formatted text might lead to ingestion failure or no meaningful data being stored.
  • API Endpoint Issues: Network problems or changes in the API URL could cause request failures. Confirm connectivity and endpoint correctness.

Common error messages might include:

  • Unauthorized access due to missing/invalid API key.
  • Resource not found for workspace or vault IDs.
  • Validation errors if required fields are missing or invalid.

Resolving these usually involves checking credentials, verifying input parameters, and ensuring network connectivity.

Links and References

Discussion