Block 1 - Qdrant Vector Store
- Type / Role
- @n8n/n8n-nodes-langchain.vectorStoreQdrant - vectorStoreQdrant
- Config choices
- Version 1.1
This workflow is provided as-is. Please review and test before using in production.
This workflow is designed for one purpose only, to bulk upload structured JSON articles from an FTP server into a Qdrant vector database for use in LLM powered semantic search, RAG systems, or A...
@n8n/n8n-nodes-langchain.vectorstoreqdrant, n8n-nodes-base.manualtrigger, @n8n/n8n-nodes-langchain.embeddingsopenai, @n8n/n8n-nodes-langchain.documentdefaultdataloader, @n8n/n8n-nodes-langchain.textsplittercharactertextsplitter, n8n-nodes-base.stickynote, n8n-nodes-base.ftp, n8n-nodes-base.splitinbatches
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Ghaith Alsirawan.
Original n8n.io source🧠 This workflow is designed for one purpose only, to bulk-upload structured JSON articles from an FTP server into a Qdrant vector database for use in LLM-powered semantic search, RAG systems, or AI assistants.
The JSON files are pre-cleaned and contain metadata and rich text chunks, ready for vectorization. This workflow handles
{
"id": "article_001",
"title": "reseguider",
"language": "sv",
"tags": ["london", "resa", "info"],
"source": "alltomlondon.se",
"url": "https://...",
"embedded_at": "2025-04-08T15:27:00Z",
"chunks": [
{
"chunk_id": "article_001_01",
"section_title": "Introduktion",
"text": "Välkommen till London..."
},
...
]
}
✅ Automated Vector Loading Handles FTP → JSON → Qdrant in a hands-free pipeline.
✅ Clean Embedding Input Supports pre-validated chunks with metadata: titles, tags, language, and article ID.
✅ AI-Ready Format Perfect for Retrieval-Augmented Generation (RAG), semantic search, or assistant memory.
✅ Flexible Architecture Modular and swappable: FTP can be replaced with GDrive/Notion/S3, and embeddings can switch to local models like Ollama.
✅ Community Friendly This template helps others adopt best practices for vector DB feeding and LLM integration.
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 | Loading JSON via FTP to Qdrant vector database embedding pipeline |
|---|---|
| Complexity | intermediate |
| Nodes | 13 |
| Categories | Engineering, AI RAG |
| Author | Ghaith Alsirawan |
| Published | 09 Apr 2025 |
Use the JSON export at /data/workflows/3495/3495.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.
This workflow is designed for one purpose only, to bulk upload structured JSON articles from an FTP server into a Qdrant vector database for use in LLM powered semantic search, RAG systems, or A...
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 Engineering, AI RAG use case.