Block 1 - Query Classification
- Type / Role
- @n8n/n8n-nodes-langchain.agent - agent
- Config choices
- Version 1.8
This workflow is provided as-is. Please review and test before using in production.
Description This workflow automatically classifies user queries and retrieves the most relevant information based on the query type. It uses adaptive strategies like; Factual, Analytical, Opinio...
@n8n/n8n-nodes-langchain.agent, n8n-nodes-base.switch, @n8n/n8n-nodes-langchain.chattrigger, n8n-nodes-base.set, @n8n/n8n-nodes-langchain.lmchatgooglegemini, @n8n/n8n-nodes-langchain.memorybufferwindow, @n8n/n8n-nodes-langchain.embeddingsgooglegemini, n8n-nodes-base.stickynote
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Nisa.
Original n8n.io sourceDescription This workflow automatically classifies user queries and retrieves the most relevant information based on the query type. π It uses adaptive strategies like; Factual, Analytical, Opinion, and Contextual to deliver more precise and meaningful responses by leveraging n8n's flexibility. Integrated with Qdrant vector store and Google Gemini, it processes each query faster and more effectively. π
How It Works? Query Reception: A user query is triggered (e.g., through a chatbot interface). π¬
Classification: The query is classified into one of four categories:
Factual: Queries seeking verifiable information.
Analytical: Queries that require in-depth analysis or explanation.
Opinion: Queries looking for different perspectives or subjective viewpoints.
Contextual: Queries specific to the user or certain contextual conditions.
Adaptive Strategy Application: Based on classification, the query is restructured using the relevant strategy for better results.
Response Generation**: The most relevant documents and context are used to generate a tailored response. π―
Set Up Steps
Estimated Time: β³ 10-15 minutes Prerequisites: You need an n8n account and a Qdrant vector store connection. Steps:
Import the n8n workflow: Load the workflow into your n8n instance.
Connect Google Gemini and Qdrant: Link these tools for query processing and data retrieval.
Connect the Trigger Interface: Integrate with a chatbot or API to trigger the workflow.
Customize: Adjust settings based on the query types you want to handle and the output format. π§
For more detailed instructions, please check the sticky notes inside the workflow. π
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.
Showing the first 24 of 40 workflow blocks. Download the JSON for the full node graph.
| Workflow | Adaptive RAG with Google Gemini & Qdrant: context-aware query answering |
|---|---|
| Complexity | advanced |
| Nodes | 40 |
| Categories | Internal Wiki, AI RAG |
| Author | Nisa |
| Published | 14 May 2025 |
Use the JSON export at /data/workflows/4043/4043.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.
Description This workflow automatically classifies user queries and retrieves the most relevant information based on the query type. It uses adaptive strategies like; Factual, Analytical, Opinio...
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.