Gmail assistant with full Gmail history RAG using OpenAI
🧠 RAG with Full Gmail history + Real time email updates in RAG using OpenAI & Qdrant
> Summary:
> This workflow listens for new Gmail messages, extracts and cleans email content, generates embeddings via OpenAI, stores them in a Qdrant vector database, and then enables a Retrieval‑Augmented‑Generation (RAG) agent to answer user queries against those stored emails. It’s designed for teams or bots that need conversational access to past emails.
🧑🤝🧑 Who’s it for
- Support teams who want to surface past customer emails in chatbots or help‑desk portals
- Sales ops that need AI‑powered summaries and quick lookup of email histories
- Developers building RAG agents over email archives
⚙️ How it works / What it does
- Trigger
- Gmail Trigger polls every minute for new messages.
- Fetch & Clean
- Get Mail Data pulls full message metadata and body.
- Code node normalizes the body (removes line breaks, collapses spaces).
- Embed & Store
- Embeddings OpenAI node computes vector embeddings.
- Qdrant Vector Store inserts embeddings + metadata into the
emails_historycollection.
- Batch Processing
- SplitInBatches handles large inbox loads in chunks of 50.
- RAG Interaction
- When chat message received → RAG Agent → uses Qdrant Email Vector Store as a tool to retrieve relevant email snippets before responding.
- Memory
- Simple Memory buffer ensures the agent retains recent context.
🛠️ How to set up
- n8n Instance
- Deploy n8n (self‑hosted or via Coolify/Docker).
- Credentials
- Create an OAuth2 credential in n8n for Gmail (with Gmail API scopes).
- Add your OpenAI API key in n8n credentials.
- Qdrant
- Stand up a Qdrant instance (self‑hosted or Qdrant Cloud).
- Note your host, port, and API key (if any).
- Import Workflow
- In n8n, go to Workflows → Import → paste the JSON you provided.
- Ensure each credential reference (Gmail & OpenAI) matches your n8n credential IDs.
- Test
- Click Execute Workflow or send a test email to your Gmail.
- Monitor n8n logs: you should see new points in Qdrant and RAG responses.
📋 Requirements
- n8n (Self-hosted or Cloud)
- Gmail API enabled on a Google Cloud project
- OpenAI API access (with Embedding & Chat endpoints)
- Qdrant (hosted or cloud) with a collection named
emails_history
🎨 How to customize the workflow
- Change Collection Name
- Update the
qdrantCollection.valuein all Qdrant nodes if you prefer a different collection.
- Update the
- Adjust Polling Frequency
- In the Gmail Trigger node, switch from
everyMinutetoeveryFiveMinutesor a webhook‑style trigger.
- In the Gmail Trigger node, switch from
- Metadata Tags
- In Enhanced Default Data Loader, tweak the
metadataValuesto tag by folder, label, or sender domain.
- In Enhanced Default Data Loader, tweak the
- Batch Size
- In SplitInBatches, change
batchSizeto suit your inbox volume.
- In SplitInBatches, change
- RAG Agent Prompt
- Customize the
systemMessagein the RAG Agent node to set the assistant’s tone, instruct on date handling, or add additional tools.
- Customize the
- Additional Tools
- Chain other n8n nodes (e.g., Slack, Discord) after the RAG Agent to broadcast AI answers to team channels.
n8n Gmail Assistant with Full Gmail History RAG using OpenAI
This n8n workflow creates a powerful AI assistant that can answer questions based on your entire Gmail history. It leverages Retrieval Augmented Generation (RAG) by fetching your emails, embedding them, storing them in a vector database (Qdrant), and then using an OpenAI Chat Model to answer queries with context from your emails.
What it does
This workflow automates the following steps:
- Triggers on Chat Message: The workflow is activated when a chat message is received (likely from an n8n chat interface or a connected chat platform).
- Fetches Gmail History: It retrieves all emails from your configured Gmail account.
- Processes Emails in Batches: Emails are processed in batches to manage large datasets efficiently.
- Extracts and Prepares Email Content: A Code node extracts relevant text content from each email.
- Splits Text into Chunks: The extracted email content is split into smaller, manageable chunks using a Character Text Splitter, which is crucial for effective RAG.
- Generates Embeddings: OpenAI Embeddings are created for each text chunk, converting them into numerical vectors.
- Stores Embeddings in Qdrant: These embeddings, along with their original text, are stored in a Qdrant Vector Store, making them searchable by semantic similarity.
- Answers Questions with AI Agent: An AI Agent (powered by an OpenAI Chat Model) uses the Qdrant Vector Store as a tool to retrieve relevant email context when answering user questions.
- Maintains Conversation History: A Simple Memory node helps the AI Agent remember previous turns in the conversation, providing a more coherent chat experience.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n Instance: A running n8n instance.
- Gmail Account: A Google account with Gmail enabled, and an n8n Google OAuth credential configured for Gmail access.
- OpenAI API Key: An OpenAI API key with access to embedding models (e.g.,
text-embedding-ada-002) and chat models (e.g.,gpt-3.5-turbo,gpt-4). - Qdrant Instance: Access to a Qdrant vector database instance (either self-hosted or cloud-based). You'll need to configure an n8n Qdrant credential.
Setup/Usage
- Import the workflow: Download the JSON provided and import it into your n8n instance.
- Configure Credentials:
- Gmail: Set up a Google OAuth2 credential for Gmail. Ensure it has the necessary permissions to read your emails.
- OpenAI: Configure an OpenAI API key credential.
- Qdrant: Set up a Qdrant credential, providing your Qdrant host and API key.
- Initial Data Loading (Manual Trigger):
- The workflow includes a "Manual Trigger" and a "Gmail Trigger". The "Gmail Trigger" is for real-time updates, but for the initial loading of your entire email history, you might want to temporarily connect the "Manual Trigger" to the "Gmail" node (Node ID 356) and execute the workflow once. This will fetch and embed your existing emails into Qdrant.
- Important: After the initial load, reconnect the "Gmail Trigger" to the "Loop Over Items" node (Node ID 39) to process new emails.
- Configure Nodes:
- Gmail Trigger (Node ID 824): Ensure this is configured to listen for new emails in your desired inbox.
- Gmail (Node ID 356): This node is used to fetch the full history. Configure it with your Gmail credential and any specific filters if you don't want to process all emails.
- Code (Node ID 834): Review the JavaScript code to understand how email content is extracted. You might need to adjust it based on the specific parts of emails you want to use for RAG.
- Character Text Splitter (Node ID 1189): Adjust
chunkSizeandchunkOverlapparameters if needed to optimize how your email text is broken down for embeddings. - Embeddings OpenAI (Node ID 1141): Select your OpenAI credential and the desired embedding model.
- Qdrant Vector Store (Node ID 1248): Select your Qdrant credential and specify a collection name. This is where your email embeddings will be stored.
- OpenAI Chat Model (Node ID 1153): Select your OpenAI credential and the desired chat model (e.g.,
gpt-4,gpt-3.5-turbo). - AI Agent (Node ID 1119): This node orchestrates the RAG process. Ensure it's correctly linked to the "Qdrant Vector Store" as a tool and the "OpenAI Chat Model" as its language model.
- Activate the Workflow: Once all credentials and nodes are configured, activate the workflow.
Now, when you send a message to the "Chat Trigger", the AI Agent will use your Gmail history stored in Qdrant to provide context-aware answers.
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 invoice processing with OCR, GPT-4 & Salesforce opportunity creation
PDF Invoice Extractor (AI) End-to-end pipeline: Watch Drive ➜ Download PDF ➜ OCR text ➜ AI normalize to JSON ➜ Upsert Buyer (Account) ➜ Create Opportunity ➜ Map Products ➜ Create OLI via Composite API ➜ Archive to OneDrive. --- Node by node (what it does & key setup) 1) Google Drive Trigger Purpose: Fire when a new file appears in a specific Google Drive folder. Key settings: Event: fileCreated Folder ID: google drive folder id Polling: everyMinute Creds: googleDriveOAuth2Api Output: Metadata { id, name, ... } for the new file. --- 2) Download File From Google Purpose: Get the file binary for processing and archiving. Key settings: Operation: download File ID: ={{ $json.id }} Creds: googleDriveOAuth2Api Output: Binary (default key: data) and original metadata. --- 3) Extract from File Purpose: Extract text from PDF (OCR as needed) for AI parsing. Key settings: Operation: pdf OCR: enable for scanned PDFs (in options) Output: JSON with OCR text at {{ $json.text }}. --- 4) Message a model (AI JSON Extractor) Purpose: Convert OCR text into strict normalized JSON array (invoice schema). Key settings: Node: @n8n/n8n-nodes-langchain.openAi Model: gpt-4.1 (or gpt-4.1-mini) Message role: system (the strict prompt; references {{ $json.text }}) jsonOutput: true Creds: openAiApi Output (per item): $.message.content → the parsed JSON (ensure it’s an array). --- 5) Create or update an account (Salesforce) Purpose: Upsert Buyer as Account using an external ID. Key settings: Resource: account Operation: upsert External Id Field: taxid_c External Id Value: ={{ $json.message.content.buyer.tax_id }} Name: ={{ $json.message.content.buyer.name }} Creds: salesforceOAuth2Api Output: Account record (captures Id) for downstream Opportunity. --- 6) Create an opportunity (Salesforce) Purpose: Create Opportunity linked to the Buyer (Account). Key settings: Resource: opportunity Name: ={{ $('Message a model').item.json.message.content.invoice.code }} Close Date: ={{ $('Message a model').item.json.message.content.invoice.issue_date }} Stage: Closed Won Amount: ={{ $('Message a model').item.json.message.content.summary.grand_total }} AccountId: ={{ $json.id }} (from Upsert Account output) Creds: salesforceOAuth2Api Output: Opportunity Id for OLI creation. --- 7) Build SOQL (Code / JS) Purpose: Collect unique product codes from AI JSON and build a SOQL query for PricebookEntry by Pricebook2Id. Key settings: pricebook2Id (hardcoded in script): e.g., 01sxxxxxxxxxxxxxxx Source lines: $('Message a model').first().json.message.content.products Output: { soql, codes } --- 8) Query PricebookEntries (Salesforce) Purpose: Fetch PricebookEntry.Id for each Product2.ProductCode. Key settings: Resource: search Query: ={{ $json.soql }} Creds: salesforceOAuth2Api Output: Items with Id, Product2.ProductCode (used for mapping). --- 9) Code in JavaScript (Build OLI payloads) Purpose: Join lines with PBE results and Opportunity Id ➜ build OpportunityLineItem payloads. Inputs: OpportunityId: ={{ $('Create an opportunity').first().json.id }} Lines: ={{ $('Message a model').first().json.message.content.products }} PBE rows: from previous node items Output: { body: { allOrNone:false, records:[{ OpportunityLineItem... }] } } Notes: Converts discount_total ➜ per-unit if needed (currently commented for standard pricing). Throws on missing PBE mapping or empty lines. --- 10) Create Opportunity Line Items (HTTP Request) Purpose: Bulk create OLIs via Salesforce Composite API. Key settings: Method: POST URL: https://<your-instance>.my.salesforce.com/services/data/v65.0/composite/sobjects Auth: salesforceOAuth2Api (predefined credential) Body (JSON): ={{ $json.body }} Output: Composite API results (per-record statuses). --- 11) Update File to One Drive Purpose: Archive the original PDF in OneDrive. Key settings: Operation: upload File Name: ={{ $json.name }} Parent Folder ID: onedrive folder id Binary Data: true (from the Download node) Creds: microsoftOneDriveOAuth2Api Output: Uploaded file metadata. --- Data flow (wiring) Google Drive Trigger → Download File From Google Download File From Google → Extract from File → Update File to One Drive Extract from File → Message a model Message a model → Create or update an account Create or update an account → Create an opportunity Create an opportunity → Build SOQL Build SOQL → Query PricebookEntries Query PricebookEntries → Code in JavaScript Code in JavaScript → Create Opportunity Line Items --- Quick setup checklist 🔐 Credentials: Connect Google Drive, OneDrive, Salesforce, OpenAI. 📂 IDs: Drive Folder ID (watch) OneDrive Parent Folder ID (archive) Salesforce Pricebook2Id (in the JS SOQL builder) 🧠 AI Prompt: Use the strict system prompt; jsonOutput = true. 🧾 Field mappings: Buyer tax id/name → Account upsert fields Invoice code/date/amount → Opportunity fields Product name must equal your Product2.ProductCode in SF. ✅ Test: Drop a sample PDF → verify: AI returns array JSON only Account/Opportunity created OLI records created PDF archived to OneDrive --- Notes & best practices If PDFs are scans, enable OCR in Extract from File. If AI returns non-JSON, keep “Return only a JSON array” as the last line of the prompt and keep jsonOutput enabled. Consider adding validation on parsing.warnings to gate Salesforce writes. For discounts/taxes in OLI: Standard OLI fields don’t support per-line discount amounts directly; model them in UnitPrice or custom fields. Replace the Composite API URL with your org’s domain or use the Salesforce node’s Bulk Upsert for simplicity.