Block 1 - Create Agent
- Type / Role
- n8n-nodes-contextualai.contextualAi - contextualAi
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
PROBLEM Managing multiple RAG AI agents can be complex when each has its own purpose and vector database. Manually tracking agents and deciding which one to query wastes time. LLMs often struggle t...
n8n-nodes-contextualai.contextualai, n8n-nodes-base.formtrigger, n8n-nodes-base.code, @n8n/n8n-nodes-langchain.agent, @n8n/n8n-nodes-langchain.chattrigger, @n8n/n8n-nodes-langchain.lmchatgooglegemini, @n8n/n8n-nodes-langchain.memorybufferwindow, n8n-nodes-contextualai.contextualaitool
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Jinash Rouniyar.
Original n8n.io sourceManaging multiple RAG AI agents can be complex when each has its own purpose and vector database.
Note: The document ingestion process is asynchronous and may take a few minutes before your agent has the document fully available in the datastore for querying.
CONTEXTUALAI_API_KEY. CONTEXTUALAI_API_KEY as an environment variable in n8n. This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.
| Workflow | Automate Document Q&A with Multi-Agent RAG Orchestration using Contextual AI & Gemini |
|---|---|
| Complexity | advanced |
| Nodes | 17 |
| Categories | Internal Wiki, AI RAG |
| Author | Jinash Rouniyar |
| Published | 09 Dec 2025 |
Use the JSON export at /data/workflows/11619/11619.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.
Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.
PROBLEM Managing multiple RAG AI agents can be complex when each has its own purpose and vector database. Manually tracking agents and deciding which one to query wastes time. LLMs often struggle t...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Internal Wiki, AI RAG use case.