Build multi-client agentic RAG document processing pipeline with Supabase Vector DB
Ultimate n8n Agentic RAG Template Author: Cole Medin What is this? This template provides a complete implementation of an Agentic RAG (Retrieval Augmented Generation) system in n8n that can be extended easily for your specific use case and knowledge base. Unlike standard RAG which only performs simple lookups, this agent can reason about your knowledge base, self-improve retrieval, and dynamically switch between different tools based on the specific question. Why Agentic RAG? Standard RAG has significant limitations: Poor analysis of numerical/tabular data Missing context due to document chunking Inability to connect information across documents No dynamic tool selection based on question type What makes this template powerful: Intelligent tool selection: Switches between RAG lookups, SQL queries, or full document retrieval based on the question Complete document context: Accesses entire documents when needed instead of just chunks Accurate numerical analysis: Uses SQL for precise calculations on spreadsheet/tabular data Cross-document insights: Connects information across your entire knowledge base Multi-file processing: Handles multiple documents in a single workflow loop Efficient storage: Uses JSONB in Supabase to store tabular data without creating new tables for each CSV Getting Started Run the table creation nodes first to set up your database tables in Supabase Upload your documents through Google Drive (or swap out for a different file storage solution) The agent will process them automatically (chunking text, storing tabular data in Supabase) Start asking questions that leverage the agent's multiple reasoning approaches Customization This template provides a solid foundation that you can extend by: Tuning the system prompt for your specific use case Adding document metadata like summaries Implementing more advanced RAG techniques Optimizing for larger knowledge bases --- I do intend on making a local version of this agent very soon!
By Growth AIDual-channel workflow error alerts with WhatsApp & Gmail reporting
Error Handler: WhatsApp Alert & Gmail Report for Failed Workflows 🎯 What This Template Does / How it Works This template provides a robust, two-step system for handling critical errors in your n8n workflows. It ensures that no workflow failure goes unnoticed, immediately notifying your team via a fast, urgent channel and providing a detailed record via a formal channel. Instant Trigger & Data Capture: The Error Trigger automatically captures all necessary metadata when an assigned workflow fails, including the error message and ID. Contact Configuration: The Set node centralizes and prepares recipient contact information (email and phone number) from the error data. Rapid Response: An urgent notification is sent via WhatsApp for immediate team awareness. Traceability & Record-Keeping: A short Wait node introduces a delay to prevent notification spam. Following the pause, a comprehensive report is sent via Gmail, ensuring a detailed record of the incident is archived. This design guarantees high-priority alerts are handled rapidly, while still maintaining essential documentation. Who’s It For This template is ideal for Ops Teams, Developers, and Automation Engineers who rely on mission-critical n8n workflows (e.g., payment processing, lead capture, data synchronization). If a failure requires immediate human intervention, this system is essential. How to Set Up Setting up this robust error handler is quick and essential for workflow stability: Configure Credentials: Ensure you have the necessary credentials added to your n8n instance for: WhatsApp Business API (for the Send message node). Gmail (for the Send Email node). Define Recipients: In the setrecipientEMAIL/NUMBER node, replace the placeholder values with the actual email address and phone number of your incident team. Activate the Listener: Open the settings of the primary workflow you wish to monitor.Go to settings ,navigate to the Error Workflow field and select the name of this template (the Error Handler). Save Changes: Save both this Error Handler workflow and the primary workflow. Done! Any failure in the primary workflow will now automatically trigger this alert system. Requirements Gmail Account (Configured as a resource). WhatsApp Business API Access (Configured as a resource and a pre-approved template available).
By rayane