Build a RAG agent with n8n, Qdrant & OpenAI
This template helps you to create an intelligent document assistant that can answer questions from uploaded files.
It shows a complete single-vector RAG (Retrieval-Augmented Generation) system that automatically processes documents, lets you chat with it in natural language and provides accurate, source-cited responses.
The workflow consists of two parts: the data loading pipeline and RAG AI Agent that answers your questions based on the uploaded documents.
To test tis workflow, you can use the following example files in a shared Google Drive folder.
💡 Find more information on creating RAG AI agents in n8n on the official page.
🔗Example files
The template uses the following example files in the Google Docs format:
- German Data Protection law: Bundesdatenschutzgesetz (BDSG)
- Computer Security Incident Handling Guide (NIST.SP.800-61r2)
- Berkshire Hathaway letter to shareholders from 2024
🚀How to get started
- Copy or import the template to your n8n instance.
- Create your Google Drive credentials via the Google Cloud Console and add them to the trigger node "Detect New Files". A detailed walk-through can be found in the n8n docs.
- Create a Qdrant API key and add it to the "Insert into Vector Store" node credentials. The API key will be displayed after you have logged into Qdrant and created a Cluster.
- Create or activate your OpenAI API key.
1️⃣ Import your data and store it in a vector database
✅ Upload files to Google Drive.
IMPORTANT: This template supports files in Google Docs format. New files will be downloaded in HTML format and converted to Markdown. This preserves the overall document structure and improves the quality of responses.
- Open the shared Google Drive folder
- Create a new folder on your Google Drive
- Activate the workflow
- Copy the files from the shared folder to your new folder
The webhook will catch the added files and you will see the execution in your "Executions" tab.
Note: If the webhook doesn’t see the files you copied, try adding them to your Google Drive folder from the opened shared files via the Move to feature.
✅ Chunk, embed, and store your data with a connected OpenAI embedding model and Qdrant vector store.
A Qdrant collection – vector storage for your data – will be created automatically after the n8n webhook has caught your data from Google Drive. You can name your collection in the "Insert into Vector Store" node.
2️⃣ Add retrieval capabilities and chat with your data
✅ Select the database with imported data in the “Search Documents” sub-node of an AI Agent.
✅ Start a chat with your agent via the chat interface: it will retrieve data from the vector store and provide a response.
❓You can ask the following questions based on the example files to test this workflow:
- What are the main steps in incident handling?
- What does Warren Buffett say about mistakes at Berkshire?
- What are the requirements for processing personal data?
- Do any documents mention data breach notification?
🌟Adapt the workflow to your own use case
- Knowledge management - Query company docs, policies, and procedures
- Research assistance - Search through academic papers and reports
- Customer support - Build agents that reference product documentation
- Legal/compliance - Query contracts, regulations, and legal documents
- Personal productivity - Chat with your notes, articles, and saved content
The workflow automatically detects new files, processes them into searchable vector chunks, and maintains conversation context. Just drop files in your Google Drive folder and start asking questions.
💻 📞Get in touch with me if you want to customise this workflow or have any questions.
n8n RAG Agent with Qdrant and OpenAI
This n8n workflow demonstrates how to build a Retrieval Augmented Generation (RAG) agent using n8n, Qdrant as a vector store, and OpenAI for embeddings and chat models. It enables your AI agent to retrieve information from a custom knowledge base (documents stored in Qdrant) before generating responses, improving the accuracy and relevance of its answers.
Description
This workflow sets up a RAG agent that can answer questions based on documents uploaded to Google Drive. It automatically processes new documents, embeds their content, stores them in a Qdrant vector database, and then uses this knowledge base to answer user queries via a chat interface.
What it does
- Triggers on new Google Drive files: The workflow starts whenever a new file is added or modified in a specified Google Drive folder.
- Loads Document Data: It retrieves the content of the new file using a Default Data Loader.
- Splits Text into Chunks: The document content is then split into smaller, manageable chunks using a Recursive Character Text Splitter to optimize for embedding and retrieval.
- Generates Embeddings: OpenAI Embeddings are generated for each text chunk.
- Stores in Qdrant: These embeddings and their corresponding text chunks are stored in a Qdrant Vector Store, creating your knowledge base.
- Listens for Chat Messages: Simultaneously, the workflow listens for incoming chat messages.
- Initializes AI Agent: When a chat message is received, an AI Agent is initialized with an OpenAI Chat Model and a Simple Memory to maintain conversation context.
- Retrieves Relevant Information: The AI Agent uses the Qdrant Vector Store as a tool to retrieve relevant document chunks based on the user's query.
- Generates Response: Finally, the AI Agent uses the retrieved information and the OpenAI Chat Model to formulate a comprehensive and contextually relevant response to the user's question.
Prerequisites/Requirements
- n8n Instance: A running n8n instance (self-hosted or cloud).
- Google Drive Account: To trigger on new document uploads.
- OpenAI API Key: For generating embeddings and using the chat model.
- Qdrant Instance: A running Qdrant vector database (can be self-hosted or cloud-managed).
- Qdrant API Key: If your Qdrant instance requires authentication.
Setup/Usage
- Import the workflow: Download the JSON provided and import it into your n8n instance.
- Configure Credentials:
- Google Drive Trigger: Set up your Google Drive OAuth2 credential. Specify the folder you want to monitor for new documents.
- OpenAI Embeddings & Chat Model: Configure your OpenAI API Key credential.
- Qdrant Vector Store: Provide your Qdrant API URL and API Key (if applicable).
- Activate the workflow: Ensure the workflow is active to start processing new Google Drive files and responding to chat messages.
- Upload Documents: Upload your knowledge base documents (e.g., text files, PDFs) to the specified Google Drive folder. The workflow will automatically process them and add them to Qdrant.
- Interact with the Chat Trigger: Use the "When chat message received" node to simulate or integrate with a chat interface (e.g., a custom webhook, a messaging app integration) to ask questions to your RAG agent.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
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
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte