Skip to main content

🤖 AI powered RAG chatbot for your docs + Google Drive + Gemini + Qdrant

Workflow preview

Workflow preview
100%
🤖 AI powered RAG chatbot for your docs + Google Drive + Gemini + Qdrant preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

AI Powered RAG Chatbot with Google Drive Integration This workflow creates a powerful RAG (Retrieval Augmented Generation) chatbot that can process, store, and interact with documents from Googl...

Best for

  • Internal Wiki automation workflows
  • AI RAG automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

@n8n/n8n-nodes-langchain.documentdefaultdataloader, @n8n/n8n-nodes-langchain.textsplittertokensplitter, @n8n/n8n-nodes-langchain.vectorstoreqdrant, n8n-nodes-base.splitinbatches, n8n-nodes-base.wait, n8n-nodes-base.manualtrigger, @n8n/n8n-nodes-langchain.lmchatgooglegemini, n8n-nodes-base.merge

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Joseph LePage.

Original n8n.io source

1.1 Workflow description

Title
🤖 AI powered RAG chatbot for your docs + Google Drive + Gemini + Qdrant
Workflow name
🤖 AI powered RAG chatbot for your docs + Google Drive + Gemini + Qdrant

🤖 AI-Powered RAG Chatbot with Google Drive Integration

This workflow creates a powerful RAG (Retrieval-Augmented Generation) chatbot that can process, store, and interact with documents from Google Drive using Qdrant vector storage and Google's Gemini AI.

How It Works

Document Processing & Storage 📚

  • Retrieves documents from a specified Google Drive folder
  • Processes and splits documents into manageable chunks
  • Extracts metadata using AI for enhanced search capabilities
  • Stores document vectors in Qdrant for efficient retrieval

Intelligent Chat Interface 💬

  • Provides a conversational interface powered by Google Gemini
  • Uses RAG to retrieve relevant context from stored documents
  • Maintains chat history in Google Docs for reference
  • Delivers accurate, context-aware responses

Vector Store Management 🗄️

  • Features secure delete operations with human verification
  • Includes Telegram notifications for important operations
  • Maintains data integrity with proper version control
  • Supports batch processing of documents

Setup Steps

  1. Configure API Credentials:

    • Set up Google Drive & Docs access
    • Configure Gemini AI API
    • Set up Qdrant vector store connection
    • Add Telegram bot for notifications
    • Add OpenAI Api Key to the 'Delete Qdrant Points by File ID' node
  2. Configure Document Sources:

    • Set Google Drive folder ID
    • Define Qdrant collection name
    • Set up document processing parameters
  3. Test and Deploy:

    • Verify document processing
    • Test chat functionality
    • Confirm vector store operations
    • Check notification system

This workflow is ideal for organizations needing to create intelligent chatbots that can access and understand large document repositories while maintaining context and providing accurate responses through RAG technology.

1.2 Logical Blocks

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.

2. Block-by-Block Analysis

Block 1 - Data Loader

Type / Role
@n8n/n8n-nodes-langchain.documentDefaultDataLoader - documentDefaultDataLoader
Config choices
Version 1

Block 2 - Token Splitter

Type / Role
@n8n/n8n-nodes-langchain.textSplitterTokenSplitter - textSplitterTokenSplitter
Config choices
Version 1

Block 3 - Qdrant Vector Store

Type / Role
@n8n/n8n-nodes-langchain.vectorStoreQdrant - vectorStoreQdrant
Config choices
Version 1

Block 4 - Loop Over Items

Type / Role
n8n-nodes-base.splitInBatches - splitInBatches
Config choices
Version 3

Block 5 - Wait

Type / Role
n8n-nodes-base.wait - wait
Config choices
Version 1.1

Block 6 - When clicking ‘Test workflow’

Type / Role
n8n-nodes-base.manualTrigger - manualTrigger
Config choices
Version 1

Block 7 - Google Gemini Chat Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatGoogleGemini - lmChatGoogleGemini
Config choices
Version 1

Block 8 - Merge

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3

Block 9 - Extract Meta Data

Type / Role
@n8n/n8n-nodes-langchain.informationExtractor - informationExtractor
Config choices
Version 1

Block 10 - Get File Contents

Type / Role
n8n-nodes-base.extractFromFile - extractFromFile
Config choices
Version 1

Block 11 - Download File From Google Drive

Type / Role
n8n-nodes-base.googleDrive - googleDrive
Config choices
Version 3

Block 12 - Find File Ids in Google Drive Folder

Type / Role
n8n-nodes-base.googleDrive - googleDrive
Config choices
Version 3

Block 13 - text-embeddings-3-large

Type / Role
@n8n/n8n-nodes-langchain.embeddingsOpenAi - embeddingsOpenAi
Config choices
Version 1

Block 14 - Google Folder ID

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 15 - gpt-4o-mini1

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1

Block 16 - Delete Qdrant Points by File ID

Type / Role
@n8n/n8n-nodes-langchain.code - code
Config choices
Version 1

Block 17 - Qdrant Collection Name

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 18 - File Id List

Type / Role
n8n-nodes-base.summarize - summarize
Config choices
Version 1.1

Block 19 - Merge1

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3

Block 20 - Merge2

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3

Block 21 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 22 - Confirm Qdrant Delete Points

Type / Role
n8n-nodes-base.telegram - telegram
Config choices
Version 1.2

Block 23 - If

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 24 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Showing the first 24 of 50 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

Workflow 🤖 AI powered RAG chatbot for your docs + Google Drive + Gemini + Qdrant
Complexity advanced
Nodes 50
Categories Internal Wiki, AI RAG
Author Joseph LePage
Published 23 Feb 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/2982/2982.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

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.

Frequently asked questions

What does 🤖 AI powered RAG chatbot for your docs + Google Drive + Gemini + Qdrant do?

AI Powered RAG Chatbot with Google Drive Integration This workflow creates a powerful RAG (Retrieval Augmented Generation) chatbot that can process, store, and interact with documents from Googl...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

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.