Back to Catalog

Gmail to vector embeddings with PGVector and Ollama

Alfonso CorrettiAlfonso Corretti
3306 views
2/3/2026
Official Page

Gmail to Vector Embeddings with PGVector and Ollama

Who is this for?

Everyone! Did you dream of asking an AI "what hotel did I stay in for holidays last summer?" or "what were my marks last semester like?".

Dream no more, as vector similarity searches and this workflow are the foundations to make it possible (as long as the information appears in your e-mails ๐Ÿ˜…).

100% local

This workflow is designed to use locally-hosted open source. Ollama as LLM provider, nomic-embed-text as the embeddings model, and pgvector as the vector database engine, on top of Postgres.

But.. how?!

Firstly, specify the date you created your Gmail account on, then manually run the workflow in order to bulk read all your e-mail in monthly batches. Your database is now populated!

Now it's the task for other workflows to query the vector database.

Activate the workflow so that new e-mail is continuously added by the Gmail Trigger upon receiving it.

Structured AND Vectorized

This workflow stores your e-mail activity in two ways:

  • In a structured table
  • In a vector embeddings table

And the information in both of them can be correlated by Gmail's messages id, which is stored in the vectors table as metadata property emails_metadata.id.

That way consumers can benefit from both worlds! โœจ Vector similarity searches enable semantic searches, while structured queries can retrieve more factual data like the message id, its date or who it came from.

Other useful templates

My template Chat with Your Email History using Telegram, Mistral and Pgvector for RAG is a ready-made solution to consume this workflow.

You may also pair this workflow with my other template to Email Assistant: Convert Natural Language to SQL Queries with Phi4-mini and PostgreSQL and you'll enable RAG workflows that use both structured and vectorized databases.

Customizations

I suppose the e-mail provider could be changed, but then you'd have to identify an alternative id field. Message-ID would be a more standard option.

There are a few opinionated choices as to what metadata to store, but those shouldn't need adjustments.

Gmail to Vector Embeddings with PGVector and Ollama

This n8n workflow automates the process of extracting email content from Gmail, converting it into vector embeddings using Ollama, and storing these embeddings in a PostgreSQL database with the PGVector extension. This allows for semantic search and AI-powered analysis of your email data.

What it does

This workflow simplifies and automates the following steps:

  1. Triggers on new Gmail messages: It listens for new emails arriving in a specified Gmail account.
  2. Filters out unwanted emails: It includes an "If" node, suggesting a conditional check to process only relevant emails. (The specific condition is not visible in the JSON but implies filtering logic).
  3. Extracts and Prepares Email Content: The workflow processes the email body and subject.
  4. Splits text into manageable chunks: It uses a "Recursive Character Text Splitter" to break down long email content into smaller, more digestible pieces suitable for embedding.
  5. Generates Vector Embeddings: It leverages Ollama to create vector embeddings from the text chunks.
  6. Stores Embeddings in PGVector: The generated vector embeddings, along with the original email content and metadata, are then stored in a PostgreSQL database configured with the PGVector extension.

Prerequisites/Requirements

To use this workflow, you will need:

  • n8n Instance: A running n8n instance.
  • Gmail Account: An active Gmail account with appropriate permissions for n8n to access.
  • Ollama Instance: A running Ollama instance accessible from your n8n environment, configured with the desired embedding model.
  • PostgreSQL Database with PGVector: A PostgreSQL database with the pgvector extension installed and enabled. You'll need database credentials (host, port, database name, user, password).
  • n8n Langchain Nodes: Ensure you have the @n8n/n8n-nodes-langchain package installed in your n8n instance to use the Text Splitter, Ollama Embeddings, and PGVector nodes.

Setup/Usage

  1. Import the Workflow:
    • Download the provided JSON file.
    • In your n8n instance, click "Workflows" in the left sidebar.
    • Click "New" and then "Import from JSON".
    • Paste the workflow JSON or upload the file.
  2. Configure Credentials:
    • Gmail Trigger: Configure your Gmail OAuth2 credentials.
    • Ollama Embeddings: Configure the connection to your Ollama instance.
    • Postgres PGVector Store: Configure your PostgreSQL database credentials.
  3. Customize the "If" Node:
    • The "If" node (ID 20) is currently a placeholder. You will need to configure its conditions to filter emails based on your specific needs (e.g., sender, subject keywords, labels).
  4. Activate the Workflow:
    • Once all credentials are set and the workflow is configured, activate it by toggling the "Active" switch in the top right corner of the workflow editor.

The workflow will now automatically process new emails according to your defined filters, generate embeddings, and store them in your PGVector database.

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.

Ranjan DailataBy Ranjan Dailata
161

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

Daniel NkenchoBy Daniel Nkencho
601

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

Wessel BulteBy Wessel Bulte
247