Voice AI chatbot with OpenAI, RAG (Qdrant) & Guardrails for WordPress
This workflow implements a complete Voice AI Chatbot system for Wordress that integrates speech recognition, guardrails for safety, retrieval-augmented generation (RAG), Qdrant vector search, and audio responses. It is designed to be connected to a WordPress Voicebot AI plugin through a webhook endpoint.
Key Advantages
-
✅ Complete Voice AI Pipeline** The workflow handles:
- audio input
- STT
- intelligent processing
- TTS output All within a single automated process.
-
✅ Safe and Policy-Compliant Thanks to the Guardrails module, the system automatically:
- detects harmful or disallowed requests
- blocks them
- responds safely This protects both the user and the business.
-
✅ Contextual and Memory-Based Conversations The Window Buffer Memory tied to unique session IDs enables:
- continuous conversation flow
- natural dialogue
- better understanding of context
-
✅ Company-Specific Knowledge via RAG By integrating Qdrant as a vector store, the system can:
- retrieve business documentation
- give accurate and up-to-date answers
- support personalized content This makes the chatbot far more powerful than a standard LLM.
-
✅ Modular and Extensible Architecture Because everything is modular inside n8n, you can:
- swap OpenAI with other models
- add new tools or knowledge sources
- change prompts or capabilities without redesigning the entire workflow.
-
✅ **Easy WordPress Integration The workflow connects directly to a WordPress Voicebot plugin, meaning:
- no custom backend development
- simple deployment
- fast integration for websites
-
✅ Automatic Indexing of Documents The second workflow section:
- fetches Google Drive files
- converts them into embeddings
- indexes them into Qdrant This lets you maintain your knowledge base with almost no manual work.
How It Works
This workflow creates a Wordpress voice-enabled AI chatbot that processes audio inputs and provides contextual responses using RAG (Retrieval-Augmented Generation) from a Qdrant vector database. The system operates as follows:
-
Audio Processing Pipeline:
- Receives audio input via webhook and converts speech to text using OpenAI's STT (Speech-to-Text)
- Applies guardrails to detect inappropriate content or jailbreak attempts using a separate GPT-4.1-mini model
- Routes safe queries to the AI agent and blocks unsafe content with a default response
-
AI Agent with Contextual Memory:
- Uses OpenAI Chat Model with window buffer memory to maintain conversation context
- Equips the agent with two tools: Calculator for computations and RAG tool for business knowledge retrieval
- The RAG system queries Qdrant vector store containing company documents using OpenAI embeddings
-
Response Generation:
- Generates appropriate text responses based on query type and available knowledge
- Converts approved responses to audio using OpenAI's TTS (Text-to-Speech) with "onyx" voice
- Returns binary audio responses to the webhook caller
Set Up Steps
-
Vector Database Preparation:
- Create Qdrant collection via HTTP request with specified vector configuration
- Clear existing collection data before adding new documents
- Set up Google Drive integration to source documents from specific folders
-
Document Processing Pipeline:
- Search and retrieve files from Google Drive folder "Test Negozio"
- Process documents through recursive text splitting (500 chunk size, 50 overlap)
- Generate embeddings using OpenAI and store in Qdrant vector store
- Implement batch processing with 5-second delays between operations
-
System Configuration:
- Configure webhook endpoint for receiving audio inputs
- Set up multiple OpenAI accounts for different functions (STT, TTS, guardrails, main agent)
- Establish Qdrant API connections for vector storage and retrieval
- Implement session-based memory management using session IDs from webhook headers
-
WordPress Integration:
- Install the provided Voicebot AI Agent WordPress plugin
- Configure the plugin with the webhook URL to connect to this n8n workflow
- The system is now ready to receive audio queries and respond with voice answers
The workflow handles both real-time voice queries and background document processing, creating a comprehensive voice assistant solution with business-specific knowledge retrieval capabilities.
Need help customizing?
Contact me for consulting and support or add me on Linkedin.
Voice AI Chatbot with OpenAI, RAG (Qdrant), and Guardrails for WordPress
This n8n workflow creates a sophisticated voice AI chatbot backend, integrating OpenAI for conversational AI, Qdrant for Retrieval Augmented Generation (RAG) to provide context from documents, and Guardrails for safety and moderation. It's designed to respond to webhook triggers, process audio input (implied by the "Voice AI" in the directory name, though not explicitly in the JSON), generate AI responses, and apply content moderation.
What it does
This workflow automates the following steps:
- Listens for incoming requests: It acts as an API endpoint, waiting for external systems (e.g., a voice interface, a WordPress plugin) to send data via a webhook.
- Loads documents from Google Drive: Retrieves relevant documents from Google Drive, likely for use as a knowledge base for the RAG system.
- Splits documents into manageable chunks: Uses a Recursive Character Text Splitter to break down large documents into smaller, searchable segments.
- Generates embeddings: Converts the text chunks into numerical vector embeddings using OpenAI's embedding models.
- Stores embeddings in Qdrant: Populates a Qdrant vector store with the generated embeddings, creating a searchable knowledge base.
- Initializes AI components: Sets up an OpenAI Chat Model for conversational AI and a Simple Memory to maintain conversation context.
- Defines AI tools: Configures an "Answer questions with a vector store" tool (using Qdrant) and a "Calculator" tool, allowing the AI agent to perform specific actions based on the user's query.
- Sets up an AI Agent: Creates an OpenAI-powered AI agent capable of planning and executing tasks using the defined tools and memory.
- Applies Guardrails for content moderation: Integrates a Guardrails node to enforce safety policies, detect and prevent unwanted content (e.g., PII, toxic language, prompt injection) in the AI's responses.
- Responds to the incoming webhook: Sends the AI-generated and moderated response back to the system that initiated the request.
- Includes a delay: Introduces a
Waitnode, possibly for rate limiting, simulating processing time, or allowing external systems to catch up.
Prerequisites/Requirements
To use this workflow, you will need:
- n8n instance: A running n8n instance (self-hosted or cloud).
- OpenAI API Key: For accessing OpenAI's embedding and chat models.
- Qdrant instance: Access to a Qdrant vector database, configured and ready to store embeddings.
- Google Drive Account: With documents accessible for the workflow to load.
- Guardrails configuration: Depending on your specific guardrail requirements, you might need to configure the Guardrails node with appropriate policies.
Setup/Usage
- Import the workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- OpenAI: Set up your OpenAI API key credential.
- Qdrant: Configure your Qdrant connection details (host, API key if applicable).
- Google Drive: Authenticate your Google Drive account.
- Configure Nodes:
- Webhook: Activate the Webhook node and copy its URL. This URL will be the endpoint for your voice AI chatbot.
- Google Drive: Specify the folder or files in Google Drive that contain your knowledge base documents.
- Qdrant Vector Store: Ensure the collection name and other parameters match your Qdrant setup.
- AI Agent: Review and adjust the agent's prompt, tools, and memory settings as needed for your specific use case.
- Guardrails: Customize the Guardrails node with your desired moderation policies and actions.
- Activate the workflow: Once configured, activate the workflow in n8n.
- Integrate with your frontend: Use the Webhook URL to send user queries (e.g., transcribed voice input) to this n8n workflow from your voice interface or WordPress application. The workflow will then return the AI's response.
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.