Actions5
- Ingestion Actions
- Retrieval Actions
Overview
This node integrates with the Qontext API to ingest unstructured data into a specified context vault within a workspace. It is designed to handle various types of source data from different integrations, such as emails, notes, tasks, or meetings, and store them in a centralized knowledge graph for further processing or retrieval.
Common scenarios include:
- Aggregating data from multiple platforms (e.g., Hubspot, Slack, Notion) into a single searchable knowledge base.
- Ingesting meeting notes or email content automatically for organizational knowledge management.
- Centralizing task descriptions or other unstructured text data for enhanced context-aware applications.
For example, a user could use this node to ingest a Slack message (source integration: Slack, source data type: Message) identified by its unique ID into a vault dedicated to project communications.
Properties
| Name | Meaning |
|---|---|
| Workspace ID | The ID of the workspace that the context vault belongs to. |
| Context Vault ID | The ID of the vault where the data should be ingested. |
| Data Source Name | The name of the data source integration (e.g., Hubspot, Slack, Notion). |
| Data Source Type | The type of data from the source (e.g., Email, Note, Task, Meeting). |
| Data Source ID | The unique identifier of the source data item (e.g., Email ID, Note ID). |
| Text | The unstructured data content (plain or markdown text) to ingest into the vault. |
Output
The node outputs JSON data representing the response from the Qontext API after ingestion. This typically includes confirmation details about the ingested data, such as identifiers or status messages confirming successful storage.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Qontext API.
- The node communicates with the Qontext API endpoint at
https://api.staging.qontext.ai/v1. - Proper configuration of the API key credential in n8n is necessary for successful operation.
Troubleshooting
- Authentication errors: If the API key is missing, invalid, or expired, the node will fail to authenticate. Ensure the API key credential is correctly set up and valid.
- Invalid IDs: Providing incorrect workspace, vault, or source data IDs may result in errors or failed ingestion. Verify all IDs before execution.
- Empty or malformed text data: The "Text" property must contain meaningful unstructured data; empty strings or unsupported formats might cause ingestion failures.
- API connectivity issues: Network problems or incorrect base URL configurations can prevent communication with the Qontext API.
Links and References
- Qontext API Documentation (assumed based on baseURL)
- n8n documentation on Creating Custom Nodes