Actions5
- Ingestion Actions
- Retrieval Actions
Overview
The node integrates with the Qontext API to retrieve contextual information from a specified knowledge graph vault within a workspace. Specifically, the "Get Context" operation under the "Retrieval" resource allows users to submit a prompt and receive relevant context extracted from the knowledge graph. This is useful in scenarios where you want to enrich prompts or queries with background knowledge stored in a structured vault, such as enhancing chatbot responses, supporting decision-making systems, or providing detailed explanations based on curated data.
For example, a user might input a question about a product, and the node will fetch related context from the product knowledge graph to provide a more informed answer.
Properties
| Name | Meaning |
|---|---|
| Workspace ID | The unique identifier of the workspace that contains the context vault. |
| Context Vault ID | The unique identifier of the specific vault (knowledge graph) used to retrieve context. |
| Prompt | The text prompt for which the node should retrieve relevant context from the vault. |
| Additional Fields | Optional parameters: • Limit: Maximum number of results to return (default 50). • Depth: Depth level of retrieval in the knowledge graph (default 1). |
Output
The node outputs JSON data containing the retrieved context relevant to the provided prompt. The structure typically includes the matched context entries from the knowledge graph vault, potentially including metadata such as relevance scores or hierarchical depth depending on the API response.
If the node supports binary data output, it would represent any associated files or attachments linked to the context, but this is not indicated in the provided code or properties.
Dependencies
- Requires an active Qontext API key credential for authentication.
- Connects to the Qontext API endpoint at
https://api.staging.qontext.ai/v1. - The node expects the user to configure the API key securely within n8n credentials.
Troubleshooting
- Missing or invalid API key: The node will fail if the API key is not set or incorrect. Ensure the API key credential is properly configured.
- Invalid Workspace or Vault IDs: Providing incorrect IDs will result in errors or empty context results. Verify these IDs are correct and accessible.
- Prompt is required: Omitting the prompt will cause the node to error out since it is mandatory.
- Limit and Depth values: Setting very high limits or depths may lead to performance issues or timeouts; use reasonable values.
- Network issues: Connectivity problems to the Qontext API endpoint can cause failures; check network access and API availability.
Links and References
- Qontext API Documentation (Assumed official docs for further details)
- n8n Documentation on Creating Custom Nodes