n8n Template Vector Sync: Ollama Embeddings + Qdrant

Vector-syncs fresh n8n templates into Qdrant using Ollama embeddings

This n8n workflow automatically pulls the latest community workflow templates from the n8n public template catalog, converts each workflow into a sanitized searchable text document, generates Ollama embeddings, and upserts them into a Qdrant collection for local retrieval—every day at 2:00 AM.

What this workflow does

• Runs on a Schedule Trigger daily at 2:00 AM.
• Fetches template listings by calling the n8n public catalog search API (first two pages), then splits the returned workflows into individual items.
• Retrieves full workflow JSON for each template from the n8n workflow template API.
• Builds documents for embedding using workflow metadata, sticky note content, system messages, and node configuration; it also sanitizes non-printable characters.
• Scans for exposed secrets by flagging templates that match common API key/secret patterns.
• Prevents duplicate vectors by deleting existing Qdrant points whose metadata.template_id matches the templates being processed.
• Generates embeddings with Ollama using nomic-embed-text:latest and upserts documents + metadata into the Qdrant collection n8n_templates.

Use cases

• Keep a local semantic search index of n8n community templates up to date without manual importing.
• Support internal “find similar workflows” experiences for automation engineers and SaaS operators.
• Reduce risk by flagging potential exposed secrets before using template content for retrieval.

Technical details

• Integrations: n8n public template catalog API, Ollama, Qdrant (purge step calls http://qdrant:6333).
• Tech stack / nodes used: code, item lists, sticky note, http request, schedule trigger, and n8n-nodes-langchainembeddings (Ollama embeddings).
• Setup: create the Qdrant collection named n8n_templates, add Qdrant credentials in n8n, ensure Ollama has nomic-embed-text:latest, and update the purge URL/collection settings if your host/port differs.