Loading JSON via FTP to Qdrant vector database embedding pipeline
🧠 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
- Downloading from FTP
- Parsing & splitting
- Embedding with OpenAI-embedding
- Storing in Qdrant for future querying
JSON structure format for blog articles
{
"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..."
},
...
]
}
🧰 Benefits
✅ 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.
n8n Workflow: FTP JSON to Qdrant Vector Database Embedding Pipeline
This n8n workflow automates the process of ingesting JSON files from an FTP server, processing their content, generating embeddings using OpenAI, and storing these embeddings in a Qdrant vector database. This is ideal for scenarios where you need to keep a vector database updated with information from structured data files stored on an FTP server.
What it does
This workflow performs the following steps:
- Manual Trigger: The workflow starts when manually executed.
- FTP File Listing: Connects to an FTP server and retrieves a list of files.
- Loop Over Items: Iterates through each file found on the FTP server.
- Default Data Loader: Loads the content of each file. Assuming the files are JSON, this node will prepare the data for further processing.
- Character Text Splitter: Splits the loaded text content into smaller, manageable chunks. This is crucial for handling large documents and optimizing embedding generation.
- Embeddings OpenAI: Generates vector embeddings for each text chunk using the OpenAI API.
- Qdrant Vector Store: Stores the generated embeddings and their associated metadata into a Qdrant vector database.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- FTP Server Access: Credentials (host, port, username, password) for an FTP server containing the JSON files you wish to process.
- OpenAI API Key: An API key for OpenAI to generate text embeddings.
- Qdrant Instance: Access to a Qdrant vector database instance (host, port, API key if applicable).
Setup/Usage
- Import the workflow:
- Copy the provided JSON code.
- In your n8n instance, go to "Workflows" and click "New".
- Click the three dots (...) in the top right corner and select "Import from JSON".
- Paste the JSON code and click "Import".
- Configure Credentials:
- FTP Node: Click on the "FTP" node and configure your FTP server credentials.
- Embeddings OpenAI Node: Click on the "Embeddings OpenAI" node and set up your OpenAI API key credential.
- Qdrant Vector Store Node: Click on the "Qdrant Vector Store" node and configure your Qdrant connection details (host, port, API key).
- Customize Nodes (Optional):
- FTP Node: Adjust the "Operation" (e.g., "List Files", "Download File") and "Path" settings to target the specific JSON files on your FTP server.
- Character Text Splitter Node: Modify chunk size and overlap parameters as needed for your specific data and embedding requirements.
- Qdrant Vector Store Node: Configure the "Collection Name" and any other Qdrant-specific settings.
- Execute the workflow:
- Click the "Execute Workflow" button in the "When clicking ‘Execute workflow’" (Manual Trigger) node to run the workflow manually.
- Alternatively, you can activate the workflow and set up a schedule or webhook trigger if you need it to run automatically.
Related Templates
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
AI-powered code review with linting, red-marked corrections in Google Sheets & Slack
Advanced Code Review Automation (AI + Lint + Slack) Who’s it for For software engineers, QA teams, and tech leads who want to automate intelligent code reviews with both AI-driven suggestions and rule-based linting — all managed in Google Sheets with instant Slack summaries. How it works This workflow performs a two-layer review system: Lint Check: Runs a lightweight static analysis to find common issues (e.g., use of var, console.log, unbalanced braces). AI Review: Sends valid code to Gemini AI, which provides human-like review feedback with severity classification (Critical, Major, Minor) and visual highlights (red/orange tags). Formatter: Combines lint and AI results, calculating an overall score (0–10). Aggregator: Summarizes results for quick comparison. Google Sheets Writer: Appends results to your review log. Slack Notification: Posts a concise summary (e.g., number of issues and average score) to your team’s channel. How to set up Connect Google Sheets and Slack credentials in n8n. Replace placeholders (<YOURSPREADSHEETID>, <YOURSHEETGIDORNAME>, <YOURSLACKCHANNEL_ID>). Adjust the AI review prompt or lint rules as needed. Activate the workflow — reviews will start automatically whenever new code is added to the sheet. Requirements Google Sheets and Slack integrations enabled A configured AI node (Gemini, OpenAI, or compatible) Proper permissions to write to your target Google Sheet How to customize Add more linting rules (naming conventions, spacing, forbidden APIs) Extend the AI prompt for project-specific guidelines Customize the Slack message formatting Export analytics to a dashboard (e.g., Notion or Data Studio) Why it’s valuable This workflow brings realistic, team-oriented AI-assisted code review to n8n — combining the speed of automated linting with the nuance of human-style feedback. It saves time, improves code quality, and keeps your team’s review history transparent and centralized.
Auto-reply & create Linear tickets from Gmail with GPT-5, gotoHuman & human review
This workflow automatically classifies every new email from your linked mailbox, drafts a personalized reply, and creates Linear tickets for bugs or feature requests. It uses a human-in-the-loop with gotoHuman and continuously improves itself by learning from approved examples. How it works The workflow triggers on every new email from your linked mailbox. Self-learning Email Classifier: an AI model categorizes the email into defined categories (e.g., Bug Report, Feature Request, Sales Opportunity, etc.). It fetches previously approved classification examples from gotoHuman to refine decisions. Self-learning Email Writer: the AI drafts a reply to the email. It learns over time by using previously approved replies from gotoHuman, with per-classification context to tailor tone and style (e.g., different style for sales vs. bug reports). Human Review in gotoHuman: review the classification and the drafted reply. Drafts can be edited or retried. Approved values are used to train the self-learning agents. Send approved Reply: the approved response is sent as a reply to the email thread. Create ticket: if the classification is Bug or Feature Request, a ticket is created by another AI agent in Linear. Human Review in gotoHuman: How to set up Most importantly, install the gotoHuman node before importing this template! (Just add the node to a blank canvas before importing) Set up credentials for gotoHuman, OpenAI, your email provider (e.g. Gmail), and Linear. In gotoHuman, select and create the pre-built review template "Support email agent" or import the ID: 6fzuCJlFYJtlu9mGYcVT. Select this template in the gotoHuman node. In the "gotoHuman: Fetch approved examples" http nodes you need to add your formId. It is the ID of the review template that you just created/imported in gotoHuman. Requirements gotoHuman (human supervision, memory for self-learning) OpenAI (classification, drafting) Gmail or your preferred email provider (for email trigger+replies) Linear (ticketing) How to customize Expand or refine the categories used by the classifier. Update the prompt to reflect your own taxonomy. Filter fetched training data from gotoHuman by reviewer so the writer adapts to their personalized tone and preferences. Add more context to the AI email writer (calendar events, FAQs, product docs) to improve reply quality.