Workflow Templates

I used this to check for a page that had Out Of Stock not found when an item came back in stock. Set the URL for the HTTP Request node and your Webhook URL and Messages for the discord nodes.

Workflow: Auto-Translate WordPress Posts Using AI Translate Pro This n8n workflow automates the translation of WordPress blog content into any language using the AI Translate Pro API, and inserts the translated text into a Google Doc. 📌 Workflow Steps Manual Trigger Initiates the workflow manually (can be replaced with a webhook or schedule trigger). WordPress Node Retrieves a specific blog post (by ID) from your WordPress site using the REST API. HTTP Request Node Sends the blog content to AI Translate Pro via multipart/form-data. Google Docs Node Appends the translated text into a specified Google Document using Google Docs API. 🌍 API Usage: AI Translate Pro Endpoint: POST https://ai-translate-pro.p.rapidapi.com/translate.php Content-Type: multipart/form-data Required Parameters: | Field | Type | Description | |-----------|--------|-----------------------------------------| | text | string | The text or HTML content to translate | | language| string | Target language (e.g., Hindi, French) | Headers: | Header Name | Value | |---------------------|---------------------------------------| | x-rapidapi-host | ai-translate-pro.p.rapidapi.com | | x-rapidapi-key | Your RapidAPI key | ✅ Benefits of Using AI Translate Pro ⚡ Fast AI-Powered Translation – Instantly translate content with no need for manual input. 🌎 Supports Multiple Languages – Easily switch languages to serve global audiences. 🧠 Context-Aware – More accurate than basic dictionary translation tools. 🛠 Easy Integration with n8n – No-code/low-code implementation. 🗃 Content Reuse – Save translations directly into Google Docs for future use or edits. 💼 Cost-Effective – Efficient alternative to expensive manual translation services. 🛠️ Problems Solved ❌ Manual copy-pasting into Google Translate ❌ Limited or slow in-house translation ❌ Difficulty managing multilingual content ❌ Inconsistent formatting or storage ✅ With AI Translate Pro, translations are fast, automated, and saved where your team can access them instantly. ✅ Example Use Case Translate WordPress blog posts from English to Hindi. Store translated content in Google Docs for editing or reuse. Expand to multilingual sites with a simple language switch. Use AI Translate Pro in any low-code or no-code platform like n8n. 📎 Requirements WordPress REST API credentials RapidAPI access to AI Translate Pro Google Docs API service account 🔗 More Info Explore full documentation and pricing on the AI Translate Pro RapidAPI listing page. Create your free n8n account and set up the workflow in just a few minutes using the link below: 👉 Start Automating with n8n Save time, stay consistent, and grow your LinkedIn presence effortlessly!

GCalendar Smart Booking System Demo github code Try yourself 📋 Description Transform your booking chaos into streamlined automation with this production-ready GCalendar Smart Booking System. This comprehensive n8n workflow eliminates weeks of custom development by providing two powerful REST APIs that handle everything from input validation to calendar integration. What makes this special? Unlike basic booking forms, this system includes enterprise-grade features like intelligent conflict detection, public holiday awareness, business hours enforcement, and automatic Google Calendar integration with Meet links. It's battle-tested with real-world business logic including lunch breaks, timezone handling, and comprehensive error responses. Privacy & Cost Benefits: 🔐 Privately yours & free** - No need to purchase expensive booking software or worry about data breaches. Your booking data stays secure in your own Google Calendar, completely under your control. 🎯 All-in-One solution** - No manual invitation sending required. Google Calendar automatically handles attendee notifications and generates real Google Meet links for every booking, creating a seamless experience for both you and your clients. No need pay for API to get public holiday, use the google calendar free default . Perfect for rapid deployment: Whether you're building for clients, launching an MVP, or replacing expensive booking software, this template gets you from zero to production in under 15 minutes. The clean API design makes frontend integration effortless, while the robust validation ensures reliable operation at scale. Two endpoints, endless possibilities: /make-booking - Complete booking creation with multi-layer validation /check-booking-date - Real-time slot availability listing (comes with conflict detection, business hour checks) Built by developers, for developers - with comprehensive documentation, testing examples, and customization guides included. Purpose This workflow provides a webhook API endpoint that your frontend can easily integrate typically triggered by a submit button on a booking form. When the frontend calls this REST API, the workflow handles the booking logic by performing several key checks: Valid Input — Ensures all required fields are present and correctly formatted. Date & Time Validation — Confirms the requested slot falls within business hours, excludes lunch/dinner breaks, and respects public holidays. Conflict Detection — Checks for any existing bookings at the requested time to prevent overlaps. Calendar Integration — Once all checks pass, the workflow automatically creates a booking entry in your Google Calendar, keeping everything synced and visible. 🎯 Target Audience This template is perfect for: 🏥 Healthcare & Medical Professionals: Clinics, dental offices, physiotherapy centers, and medical practices needing automated appointment scheduling with proper business hours validation and no-show reduction. 💼 Professional Service Providers: Consultants, lawyers, accountants, financial advisors, and coaches who require sophisticated booking systems with calendar integration and conflict prevention. 🎓 Educational Institutions: Universities, tutoring centers, training academies, and educational consultants needing student appointment scheduling with academic calendar integration. 🏢 Small to Medium Businesses: Service-based businesses like salons, spas, repair services, and consulting firms looking to automate their booking process without expensive software subscriptions. 👨‍💻 Software Development Teams: Developers and engineering teams who need to rapidly deploy booking functionality for client projects without building from scratch. 🌐 Digital Agencies: Web development agencies, marketing firms, and digital consultancies building booking solutions for multiple clients across different industries. 🏨 Hospitality & Events: Meeting room booking, event venue scheduling, equipment rental companies, and co-working spaces requiring intelligent availability management. 🔧 Freelancers & Solo Entrepreneurs: Independent professionals like designers, photographers, personal trainers, and contractors who need professional booking systems on a budget. 📊 Product Managers: Teams building SaaS products that require booking/scheduling features as part of their core functionality or user experience. 🚀 Startup Founders: Early-stage companies needing to validate booking-related business models quickly without significant development investment. 🎨 Creative Professionals: Photographers, videographers, music instructors, and artists who need client appointment scheduling with portfolio integration possibilities. ⚙️ Technical Operations Teams: DevOps engineers and system administrators who need to implement booking systems for internal resource allocation (servers, equipment, meeting rooms). This template eliminates weeks of development time while providing enterprise-grade validation, making it ideal for anyone who values rapid deployment, reliability, and professional functionality in their booking systems. ⚙️ How It Works 🔄 Booking Flow (Step-by-Step) Phase 1: Input Validation // Real validation logic from the workflow ✅ Name, email, phone, date, time validation ✅ Email format verification (RFC compliant) ✅ Phone number format checking ✅ Date/time format standardization (YYYY-MM-DD, HH:MM) Phase 2: Business Logic Validation // Business hours: Monday-Friday, 9AM-9PM (customizable) ✅ Weekend blocking ✅ Business hours enforcement ✅ Lunch break exclusion (12PM-2PM) ✅ Dinner break exclusion (6PM-8PM) ✅ Timezone handling (Malaysia/UTC+8 default) Phase 3: Intelligent Conflict Detection // Multi-calendar checking ✅ Public holiday calendar integration ✅ Main booking calendar conflict detection ✅ Real-time availability verification ✅ Overlap prevention algorithms Phase 4: Calendar Integration // Google Calendar automation ✅ Event creation with attendee invitation ✅ Google Meet link generation ✅ Custom event descriptions and summaries ✅ Calendar color coding 🕒 Availability API Flow Date Input → Validates YYYY-MM-DD format Weekend/Holiday Check → Blocks non-working days Slot Generation → Creates available time slots Conflict Mapping → Marks booked vs available slots Response Formatting → Returns structured availability data 🛠️ Quick Start Guide Prerequisites n8n instance (cloud or self-hosted) Google Cloud Project with Calendar API enabled Google Calendar credentials Simple Setup Guide Step 1: Import the Workflow ⬇️ Download the smart-booking-system.json file In your n8n instance: Workflows → Import from File Select the downloaded JSON file Click Import Step 2: Set Up Google Calendar Credentials 🔑 Create Google Cloud Project: Go to Google Cloud Console Create new project or select existing one Enable Google Calendar API Configure n8n Credentials: In n8n: Credentials → Add Credential → Google Calendar OAuth2 API Enter your Google Cloud Client ID and Client Secret Save as "Google Calendar account" Update Workflow Nodes: Find nodes: Create Calendar Event, Check Calendar Availability, etc. Select your Google Calendar credential in each node Step 3: Configure Your Calendars 📅 Main Booking Calendar: Create a dedicated Google Calendar for bookings Copy the Calendar ID (found in Calendar Settings) Replace YOUR_BOOKING_CALENDAR_ID@group.calendar.google.com in these nodes: Create Calendar Event Check Calendar Availability - Main Check Calendar Availability Holiday Calendar (Optional): Add your country's holiday calendar to Google Calendar Find the calendar ID (e.g., en.usa#holiday@group.v.calendar.google.com) Update Check Calendar Availability - public holiday and Check Public Holiday Calendar nodes Step 4: Customize Business Hours ⏰ Find the ConfigTimeSlots node Edit the time slots array: [ { "time": "09:30", "display": "9:30 AM - 10:30 AM", "available": true }, { "time": "10:30", "display": "10:30 AM - 11:30 AM", "available": true }, { "time": "11:30", "display": "11:30 AM - 12:30 PM", "available": true }, { "time": "14:30", "display": "2:30 PM - 3:30 PM", "available": true }, { "time": "15:30", "display": "3:30 PM - 4:30 PM", "available": true }, { "time": "16:30", "display": "4:30 PM - 5:30 PM", "available": true }, { "time": "17:30", "display": "5:30 PM - 6:30 PM", "available": true }, { "time": "20:30", "display": "8:30 PM - 9:30 PM", "available": true } ] Step 5: Activate & Test 🚀 Activate the workflow: Toggle the workflow Active switch Get your webhook URLs: Booking: https://your-n8n-domain/webhook/suarify-make-booking Availability: https://your-n8n-domain/webhook/suarify-check-booking-date Test with sample requests: Test booking creation curl -X POST 'https://your-n8n-domain/webhook/suarify-make-booking' \ -H 'Content-Type: application/json' \ -d '{ "name": "John Doe", "email": "john@example.com", "phone": "+1234567890", "date": "2024-03-15", "time": "14:30" }' Test availability checking curl -X POST 'https://your-n8n-domain/webhook/suarify-check-booking-date' \ -H 'Content-Type: application/json' \ -d '{"date": "2024-03-15"}' Step 6: Integrate with Your Frontend 💻 Use the webhook URLs in your booking form Handle the JSON responses for success/error states Display available time slots from the availability API 🎉 You're ready to start taking bookings! 📋 API Documentation 📤 Booking Creation API Endpoint: POST /webhook/make-booking Request Body: { "name": "John Doe", "email": "john@example.com", "phone": "+1234567890", "date": "2024-03-15", "time": "14:30", "source": "Website Form" } Success Response (200): { "success": true, "message": "Booking confirmed successfully!", "bookingDetails": { "name": "John Doe", "email": "john@example.com", "phone": "+1234567890", "date": "2024-03-15", "time": "14:30", "eventId": "abc123def456", "eventLink": "https://calendar.google.com/event?eid=...", "calendarEvent": { /* Full calendar event object */ } }, "confirmationMessage": "Hi John Doe, your booking has been confirmed for 2024-03-15 at 14:30. You will receive a calendar invitation shortly." } Error Response (400): { "success": false, "error": "Invalid email format", "message": "Booking request failed validation", "details": { /* Error context */ } } 📅 Availability Check API Endpoint: POST /webhook/check-booking-date Request Body: { "date": "2024-03-15" } Success Response (200): { "success": true, "isWorkingDay": true, "isWeekend": false, "holidayName": "", "availableSlots": [ { "time": "09:30", "display": "9:30 AM - 10:30 AM", "available": true }, { "time": "10:30", "display": "10:30 AM - 11:30 AM", "available": false, "status": "booked" } ], "totalConflicts": 3 } 🎛️ Customization Guide Business Hours Configuration Edit the ConfigTimeSlots node to modify available booking times: const timeSlots = [ { time: '09:00', display: '9:00 AM - 10:00 AM', available: true }, { time: '10:00', display: '10:00 AM - 11:00 AM', available: true }, // Lunch break automatically excluded { time: '14:00', display: '2:00 PM - 3:00 PM', available: true }, // Customize as needed... ]; Timezone Adjustment Modify the Business Hours Check node: // Change from Malaysia (UTC+8) to your timezone const timezone = 'America/New_York'; // UTC-5 const timezoneOffset = '-05:00'; Holiday Calendar Update calendar ID in holiday checking nodes: // Replace with your country's holiday calendar "value": "en.usa#holiday@group.v.calendar.google.com" Business Rules Customize validation in the Business Hours Check node: // Business hours: Mon-Fri, 9am-6pm (example) const isWithinBusinessHours = timeInMinutes >= 540 && timeInMinutes <= 1080; // Remove lunch breaks if not needed const isNotLunchBreak = true; // Always allow Start automating in under 15 minutes! 🎉 Made with ❤️ for the engineering community. Star this repo if it saves you time!

Filters articles based on keywords, checks against MongoDB for unique links, then sends results to different webhooks

CPO Agent with Product Team Description Streamline product development with an AI-powered Chief Product Officer (CPO) agent orchestrating specialized product team members for comprehensive product strategy and execution. Overview This n8n workflow creates a comprehensive product development department using AI agents. The CPO agent analyzes product opportunities and delegates tasks to specialized agents for product management, UX design, user research, analytics, documentation, and strategic planning. Features Strategic CPO agent using OpenAI O3 for complex product strategy and decision-making Six specialized product agents powered by GPT-4.1-mini for efficient execution Complete product lifecycle coverage from ideation to launch Automated user research and persona development UX/UI design specifications and wireframing Product analytics and KPI tracking Technical documentation and API specifications Team Structure CPO Agent**: Product vision and strategy coordination (O3 model) Product Manager**: Roadmaps, feature specifications, user stories, planning UX/UI Designer**: User flows, wireframes, interface design, usability User Research Specialist**: Research plans, personas, market analysis, insights Product Analytics Specialist**: Metrics, KPIs, A/B testing, data analysis Technical Writer**: Product documentation, API docs, user guides Product Strategy Analyst**: Competitive analysis, market positioning, GTM strategy How to Use Import the workflow into your n8n instance Configure OpenAI API credentials for all chat models Deploy the webhook for chat interactions Send product requests via chat (e.g., "Design a new mobile app feature for user onboarding") The CPO will analyze and delegate to appropriate specialists Receive comprehensive product deliverables and strategic insights Use Cases Feature Development**: Concept → Research → Design → Specifications → Metrics Product Launch**: Strategy → Documentation → Analytics → Go-to-market planning User Experience Optimization**: Research → Personas → User flows → Testing → Iteration Competitive Analysis**: Market research → Positioning → Differentiation strategies Product Roadmapping**: Vision → Priorities → Timeline → Resource planning Documentation Suite**: User guides → API documentation → Technical specifications Analytics Implementation**: KPI definition → Tracking setup → Performance analysis Market Research**: Customer interviews → Persona development → Requirements gathering Requirements n8n instance with LangChain nodes OpenAI API access (O3 for CPO, GPT-4.1-mini for specialists) Webhook capability for chat interactions Optional: Integration with product management tools (Jira, Figma, etc.) Cost Optimization O3 model used only for strategic CPO decisions GPT-4.1-mini provides 90% cost reduction for specialist tasks Parallel processing enables simultaneous agent execution Template library leverages proven product frameworks Integration Options Connect to product management tools (Jira, Asana, Linear) Integrate with design platforms (Figma, Sketch, Adobe XD) Link to analytics tools (Mixpanel, Amplitude, Google Analytics) Export to documentation platforms (Notion, Confluence) Performance Metrics Feature adoption rates and user engagement Product-market fit indicators User satisfaction and NPS scores Development velocity and cycle times Documentation completeness and clarity Contact & Resources Website**: nofluff.online YouTube**: @YaronBeen LinkedIn**: Yaron Been Tags #ProductManagement #UXDesign #UserResearch #ProductStrategy #ProductOps #ProductAnalytics #TechnicalWriting #ProductDevelopment #FeatureDesign #ProductAI #n8n #OpenAI #MultiAgentSystem #ProductTech #ProductLeadership #Innovation

What It Does This workflow automatically connects to the Square API and generates a daily sales summary report for all your Square locations. The report matches the figures displayed in Square Dashboard > Reports > Sales Summary. It's designed to run daily and pull the previous day's sales into a Google Sheet for easy analysis and reporting. This workflow builds on my previous template, which allows users to automatically pull data from the Square API into N8N for processing. (See here: https://n8n.io/workflows/6358) Prerequisites To use this workflow, you'll need: A Square API credential (configured as a Header Auth credential) A Google Sheets credential How to Set Up Square Credentials: Go to Credentials > Create New Choose Header Auth Set the Name to "Authorization" Set the Value to your Square Access Token (e.g., Bearer <your-api-key>) How It Works Trigger – The workflow runs daily at 4:00 AM Fetch Locations – An HTTP request retrieves all Square locations linked to your account Fetch Orders – For each location, an HTTP request pulls completed orders for the specified report_date Filter Empty Locations – Locations with no sales are ignored Aggregate Sales Data – A Code node processes the order data and produces a summary identical to Square’s Sales Summary report Append to Google Sheets – The data will automatically be appended to an existing Google sheet Example Use Cases Automatically store daily sales data in Google Sheets for analysis and historical tracking Automatically create charts or visualizations from the imported data Build weekly/monthly reports after running for multiple days Quickly calculate commissions or rent payments based on sales volume How to Use Configure both HTTP Request nodes to use your Square API credential Set the workflow to Active so it runs automatically Select the Google Sheet you want to import data into, and map the data to your columns Customization Options Add pagination to handle locations with more than 1,000 orders per day Expand the workflow to save or send the report output via other integrations (email, database, webhook, etc.) Why It's Useful This workflow saves time, reduces manual report pulling from Square, and enables smarter automation around sales data—whether for operations, finance, or performance monitoring.

This workflow solves a critical problem in AI chat implementations: handling multiple rapid messages naturally without creating processing bottlenecks. Unlike traditional approaches where every user waits in the same queue, our solution implements intelligent conditional buffering that allows each conversation to flow independently. Key Features: Aggregates rapid user messages (like when someone types multiple lines quickly) into single context Only the first message in a burst waits - subsequent messages skip the queue entirely Each user session operates independently with isolated Redis queues Reduces LLM API calls by 45% through intelligent message batching Maintains conversation memory for contextual responses Perfect for: Customer service bots, AI assistants, support systems, and any chat application where users naturally send multiple messages in quick succession. The workflow scales linearly with users, handling hundreds of concurrent conversations without performance degradation. Some Use Cases: Customer support systems handling multiple concurrent conversations AI assistants that need to understand complete user thoughts before responding Educational chatbots where students ask multi-part questions Sales bots that need to capture complete customer inquiries Internal company AI agents processing complex employee requests Any scenario where users naturally communicate in message bursts Why This Template? Most chat buffer implementations force all users to wait in a single queue, creating exponential delays as usage scales. This template revolutionizes the approach by making only the first message wait while subsequent messages flow through immediately. The result? Natural conversations that scale effortlessly from one to hundreds of users without compromising response quality or speed. Prerequisites n8n instance (v1.0.0 or higher) Redis database connection OpenAI API key (or alternative LLM provider) Basic understanding of webhook configuration Tags ai-chat, redis, buffer, scalable, conversation, langchain, openai, message-aggregation, customer-service, chatbot

n8n Graphical Input Template - AI Agent Interface A beautiful, ready-to-use HTML interface for n8n workflows that allows your users to interact with AI agents through a clean web UI. No frontend skills required! 🎯 Why Use This Template? No Frontend Skills Required**: Get a professional interface without writing React, Vue, or complex JavaScript Real-Time AI Responses**: Display AI responses directly in the interface with loading animations User-Friendly**: Your clients get a beautiful UI instead of dealing with APIs or command-line tools Plug & Play**: Just paste the code in an n8n Code node and connect your AI agents Fully Customizable**: Easy to modify colors, add more agents, or change the layout Dark/Light Mode**: Built-in theme toggle with localStorage persistence 🚀 When to Use This? Perfect for: AI Agent Interactions**: Let users chat with different specialized AI agents (Database, Web Search, RAG) Customer Support**: Route customer questions to appropriate AI assistants Data Collection**: Gather information from clients with instant AI-powered responses Customer Portals**: Create simple interfaces for customers to interact with your AI automations Internal Tools**: Build quick admin panels with AI assistance 📦 What's Included? ✅ Text Input Area: Large textarea for user messages ✅ Send Button: Main action button with smooth animations ✅ 4 Specialized Agent Buttons: Pre-configured for General, Database, Web, and RAG agents ✅ AI Response Display: Beautiful response area with agent badges and loading states ✅ Project Guide Modal: Built-in documentation for your users ✅ Theme Toggle: Dark/Light mode with localStorage persistence ✅ Responsive Design: Works perfectly on desktop, tablet, and mobile ✅ Font Awesome Icons: Beautiful icons throughout the interface ✅ Error Handling: Graceful error messages if something goes wrong 🛠️ How to Use Part 1: Display the Interface Create a 3-node workflow to show the UI: Webhook (GET) → Code Node → Respond to Webhook Configuration: Webhook Node (GET): Method: GET Path: /your-interface (e.g., /ai-chat) Authentication: Optional Code Node: Copy the entire content of main.js Paste it into the Code field Respond to Webhook: Respond With: First incoming item Response Data Source: Binary Binary Property: data Part 2: Process AI Requests Create a separate workflow to handle AI processing: Webhook (POST) → Switch → AI Agents → Code Node → Respond to Webhook Configuration: Webhook Node (POST): Method: POST Path: /webhook-endpoint Response Mode: "Respond to Webhook" Switch Node - Route by agent type: Rule 1: {{ $json.body.agent_type }} equals general Rule 2: {{ $json.body.agent_type }} equals database Rule 3: {{ $json.body.agent_type }} equals web Rule 4: {{ $json.body.agent_type }} equals rag AI Agent Nodes (4 nodes, one per agent type): Connect one AI Agent to each Switch output Configure with OpenAI, Anthropic, or local LLM Add tools, memory, system prompts as needed Code Node - Format the response: const webhookData = $('Webhook').first().json.body; const aiResponse = $input.first().json; return [{ json: { response: aiResponse.output || aiResponse.text || aiResponse.response, agent_type: webhookData.agent_type, user_message: webhookData.message, timestamp: new Date().toISOString() } }]; Respond to Webhook - Send back the formatted response 🔧 What to Update In main.js Line 847 - Update webhook URL to match your n8n path: const WEBHOOK_URL = '/webhook/webhook-endpoint'; Line 20 - Customize project name: const projectName = "AI Assistant Hub"; Lines 34-56 - Change colors (optional): :root { --primary: #6366f1; /* Main accent color */ --primary-hover: #4f46e5; /* Hover state */ --background: #ffffff; /* Background */ } 📊 How It Works User visits /your-interface ↓ Sees the chat interface ↓ Types message + clicks agent button ↓ POST to /webhook/webhook-endpoint { "message": "Find users in database", "agent_type": "database", "timestamp": "2025-10-19T..." } ↓ Switch routes to Database AI Agent ↓ AI Agent processes with tools/memory ↓ Code Node formats response ↓ Returns { "response": "Found 10 users..." } ↓ Interface displays response with badge + animation 🎨 Customization Guide Add More Agents Copy an agent card (lines ~700-730) and modify: Custom AI Agent Specialized in your custom task. Then add CSS for the new agent type: .agent-card.custom-agent::before { background: #f59e0b; } .agent-card.custom-agent:hover { border-color: #f59e0b; } .agent-icon.custom-icon { background: linear-gradient(135deg, #f59e0b, #d97706); } .response-agent-badge.custom-badge { background: rgba(245, 158, 11, 0.1); color: #f59e0b; } And update the Switch node to handle the new agent type! Modify Text Content Modal Guide**: Lines ~754-810 - Update help text Placeholder**: Line ~689 - Change textarea placeholder Subtitles**: Lines 677, 693 - Modify section descriptions Change Agent Descriptions Lines 705, 717, ~729 - Update the description text for each agent. 📱 Built-in Features Enter to Send**: Press Enter to send (Shift+Enter for new line) Escape to Close**: Press Esc to close modals Loading State**: Animated spinner while AI processes Agent Badges**: Color-coded badges show which agent responded Clear Button**: Easily clear responses to start fresh Theme Persistence**: Theme choice saved in browser Smooth Animations**: Professional transitions and hover effects Error Handling**: User-friendly error messages 💡 Example Workflow Ideas Customer Support Bot General Agent**: Answers common questions Database Agent**: Looks up order status, account info Web Agent**: Searches knowledge base articles RAG Agent**: Searches company documentation Data Analysis Tool General Agent**: Explains data concepts Database Agent**: Runs SQL queries on your data Web Agent**: Fetches external data sources RAG Agent**: Searches analysis reports Internal Admin Panel General Agent**: General assistance Database Agent**: User management queries Web Agent**: Check external integrations RAG Agent**: Search internal docs/wikis 🐛 Troubleshooting Response not displaying? Check that Code Node after AI Agent formats response with response field Verify webhook URL in main.js matches your n8n webhook path Check browser console for JavaScript errors AI Agent not responding? Ensure Switch node routes match agent types: general, database, web, rag Verify AI Agent nodes are properly configured with API keys Check n8n execution logs for errors Styling issues? Clear browser cache Check that Font Awesome CDN is loading Verify CSS variables are properly defined 📝 Technical Details Framework**: Pure HTML/CSS/JavaScript (no dependencies!) Icons**: Font Awesome 6.4.0 Browser Support**: All modern browsers (Chrome, Firefox, Safari, Edge) Mobile**: Fully responsive with touch support File Size**: 1050 lines (35KB minified) 🤝 Contributing & Support This template is designed to be simple and self-explanatory. The code structure: Lines 1-23: Configuration and setup Lines 24-640: CSS styles Lines 641-751: HTML structure Lines 752-1048: JavaScript functions Feel free to modify and adapt to your needs! 📝 License Free to use and modify for your n8n workflows. No attribution required.

LeadBot Autopilot — Chat-to-Lead for Salesforce Description — How It Works Greets & Guides: Welcomes the visitor and collects info step-by-step — Full Name → Email → Mobile → Product Interest. Validates Inputs: Checks email/phone formats; politely re-asks if invalid. De-dupe in Salesforce: Looks up by email; updates an existing lead if found. Create/Update Lead: Writes to Salesforce, including ProductInterest__c. Notify Instantly: Sends a Slack alert to your team and a personalized email to the prospect. Close the Loop: Confirms submission and ends the chat. Description — Set Up Steps (≈45–75 mins) Connect Credentials (20–30 mins):** Salesforce OAuth, OpenAI, Slack, SMTP. Tune the Prompt (5–10 mins):** Greeting, field order, product options. Map Fields (10–15 mins):** Name split, email/phone, ProductInterest__c. Smoke Test (10–15 mins):** Run a full chat; verify de-dupe, Slack + email. Go Live (5–10 mins):** Expose the webhook/chat entry point on your site.

CLO Agent with Legal Team Description Navigate legal complexities with an AI-powered Chief Legal Officer (CLO) agent orchestrating specialized legal team members for comprehensive legal operations and risk management. Overview This n8n workflow creates a comprehensive legal department using AI agents. The CLO agent analyzes legal requirements and delegates tasks to specialized agents for contract management, compliance, intellectual property, privacy law, corporate governance, and employment law. ⚠️ IMPORTANT DISCLAIMER: These AI agents provide legal information and templates, NOT legal advice. Always consult qualified legal professionals for binding legal matters. This workflow does not create attorney-client privilege or provide professional legal liability coverage. Building Blocks Approach This workflow provides foundational AI agents as building blocks for your legal operations. Feel free to: Customize agent prompts to match your industry and legal requirements Add relevant legal tools and integrations (contract management, compliance platforms) Modify specialist focus areas based on your specific legal needs Integrate with legal research databases and document management systems Adjust the CLO's strategic oversight to align with your risk tolerance Features Strategic CLO agent using OpenAI O3 for complex legal strategy and risk assessment Six specialized legal agents powered by GPT-4.1-mini for efficient execution Complete legal lifecycle coverage from contracts to compliance Automated document generation and review processes Risk assessment and mitigation strategies Intellectual property protection workflows Privacy and data protection compliance Team Structure CLO Agent**: Legal strategy and risk management coordination (O3 model) Contract Specialist**: Contract drafting, review, negotiation terms, agreement analysis Compliance Officer**: Regulatory compliance, legal requirements, audits, risk assessment IP Specialist**: Patents, trademarks, copyrights, trade secrets, IP protection Privacy Lawyer**: GDPR, CCPA, data privacy policies, data protection compliance Corporate Lawyer**: Corporate governance, M&A, securities law, business formation Employment Lawyer**: Employment contracts, workplace policies, labor law, HR legal issues How to Use Import the workflow into your n8n instance Configure OpenAI API credentials for all chat models Deploy the webhook for chat interactions Send legal requests via chat (e.g., "Draft a software licensing agreement") The CLO will analyze and delegate to appropriate specialists Receive comprehensive legal deliverables and risk assessments Use Cases Contract Lifecycle Management**: Draft → Review → Negotiate → Execute → Monitor Compliance Programs**: Policy creation → Risk assessment → Audit preparation IP Protection Strategy**: Patent applications → Trademark registration → Copyright notices Privacy Compliance**: GDPR assessments → Privacy policies → Data mapping exercises Corporate Governance**: Board resolutions → Shareholder agreements → Corporate bylaws Employment Law**: Policy manuals → Contract templates → Dispute resolution procedures Legal Document Automation**: Template creation → Review workflows → Version control Risk Assessment**: Legal risk evaluation → Mitigation strategies → Compliance monitoring Requirements n8n instance with LangChain nodes OpenAI API access (O3 for CLO, GPT-4.1-mini for specialists) Webhook capability for chat interactions Optional: Integration with legal management tools (contract management systems, legal research databases) Legal Scope & Limitations This AI workflow provides: ✅ Legal document templates and frameworks ✅ Compliance checklists and procedures ✅ Risk assessment methodologies ✅ Legal research summaries and insights This AI workflow does NOT provide: ❌ Legal advice or professional legal counsel ❌ Attorney-client privilege protection ❌ Court representation or litigation support ❌ Professional legal liability coverage ❌ Jurisdiction-specific legal opinions Cost Optimization O3 model used only for strategic CLO decisions and complex legal analysis GPT-4.1-mini provides 90% cost reduction for specialist document tasks Parallel processing enables simultaneous legal workstream execution Template library reduces redundant legal document generation Integration Options Connect to contract management systems (DocuSign, PandaDoc, ContractWorks) Integrate with legal research databases (Westlaw, LexisNexis) Link to compliance management platforms (GRC tools, audit systems) Export to document management systems (SharePoint, Box, Google Drive) Performance Metrics Contract cycle time reduction and accuracy Compliance audit success rates Legal risk identification and mitigation effectiveness Document review efficiency and consistency Cost per legal matter and resource utilization Contact & Resources Website**: nofluff.online YouTube**: @YaronBeen LinkedIn**: Yaron Been Tags #LegalTech #ContractAutomation #ComplianceTech #LegalAI #LegalOps #IntellectualProperty #PrivacyLaw #CorporateLaw #EmploymentLaw #LegalInnovation #n8n #OpenAI #MultiAgentSystem #LegalDocument #RiskManagement #LegalStrategy

This n8n workflow automates airline customer support by classifying travel-related questions, fetching relevant information, generating AI answers, and delivering structured responses to users. It ensures accurate travel information delivery, tracks user satisfaction, and logs interactions for future insights — reducing manual support load and improving customer experience. Key Features Allows users to ask airline/travel questions directly through chat via webhook integration. Automatically classifies questions into categories like baggage, refunds, visas, bookings, and travel info. Fetches verified travel knowledge and generates responses using AI. Performs satisfaction check and offers human support if needed. Logs all conversations and system responses for analytics and support auditing. Workflow Process The Webhook Entry Point node receives passenger questions from chat/website (e.g., WhatsApp, web chat widget, or API). The Data Extraction & Cleaning node formats the user query by removing noise and structuring text. The Question Categorization node uses AI to classify the inquiry (e.g., baggage policy, cancellation rules, destination info). The Category Parsing node routes the query to the appropriate context source or knowledge logic. The Knowledge Retrieval node fetches verified travel or airline-specific information. The AI Response Generator node produces a natural, accurate customer-facing reply using the retrieved context. The Response Formatting node adds clarity, structured bullet points, links, and travel guidance tips. The Satisfaction Check node asks if the user is happy with the answer and branches: If satisfied → continue to logging If not satisfied → send request to human support channel The Human Escalation Path node hands unresolved queries to human support teams. The Interaction Logger node stores conversation data (question, category, AI response, feedback status) in a database. The Final Delivery node sends the formatted response back to the user chat channel. Setup Instructions Import the workflow into n8n and configure the Webhook Entry Point with your chat platform or airline support portal. Add OpenAI API credentials in the AI Response Generator and Categorization nodes. Set up your Knowledge Retrieval source (e.g., internal travel database, API, or curated knowledge file). Connect a database (e.g., PostgreSQL, MySQL, Supabase, MongoDB) to store conversation logs and user behavior. Configure optional human support integration (Slack, email, CRM, or support desk tool). Test the workflow by sending sample airline queries (e.g., “Baggage limit to Dubai?” or “How to reschedule my flight?”). Prerequisites n8n instance with webhook, AI, and database nodes enabled. OpenAI API key for AI classification and response generation. Airline or travel knowledge source (API or internal knowledge base). Database connection for logging queries and satisfaction responses. Customer chat channel setup (WhatsApp, website widget, CRM integration, or Telegram bot). Modification Options Enhance the Knowledge Retrieval step to pull real-time data from flight APIs, visa APIs, or airline portals. Add language translation to support global passengers. Extend Satisfaction Logic to auto-escalate urgent cases (e.g., flight delays, lost baggage complaints). Build self-service functions like: Flight status lookup Refund eligibility checker Visa requirement assistant Customize the Response Formatting to include buttons/links (e.g., check baggage rules, contact support). Explore More AI Travel Workflows: Get in touch with us for custom airline automation!

SETUP INSTRUCTIONS 1. Configure Kubeconfig Open the "Kubeconfig Setup" node Paste your entire kubeconfig file content into the kubeconfigContent variable Set your target namespace in the namespace variable (default: 'production') Example kubeconfig format: apiVersion: v1 kind: Config clusters: cluster: certificate-authority-data: LS0tLS1CRUd... server: https://your-cluster.example.com:6443 name: your-cluster contexts: context: cluster: your-cluster user: your-user name: your-context current-context: your-context users: name: your-user user: token: eyJhbGciOiJSUzI1... 2. Telegram Configuration Create a Telegram bot via @BotFather Get your bot token and add it as a credential in n8n (Telegram API) Find your chat ID: Message your bot Visit: https://api.telegram.org/bot<YourBotToken>/getUpdates Look for "chat":{"id":...} Open the "Send Telegram Alert" node Replace YOUR_TELEGRAM_CHAT_ID with your actual chat ID Select your Telegram API credential 3. Schedule Configuration Open the "Schedule Trigger" node Default: runs every 1 minute Adjust the interval based on your monitoring needs: Every 5 minutes: Change field to minutes and set minutesInterval to 5 Every hour: Change field to hours and set hoursInterval to 1 Cron expression: Use custom cron schedule 4. kubectl Installation The workflow automatically downloads kubectl (v1.34.0) during execution No pre-installation required on the n8n host kubectl is downloaded and used temporarily for each execution HOW IT WORKS Workflow Steps Schedule Trigger Runs automatically based on configured interval Initiates the monitoring cycle Kubeconfig Setup Loads the kubeconfig and namespace configuration Passes credentials to kubectl commands Parallel Data Collection Get Pods: Fetches all pods from the specified namespace Get Deployments: Fetches all deployments from the specified namespace Both commands run in parallel for efficiency Process & Generate Report Parses pod and deployment data Groups pods by their owner (Deployment, DaemonSet, StatefulSet, or Node) Calculates readiness statistics for each workload Detects alerts: workloads with 0 ready pods Generates a comprehensive Markdown report including: Deployments with replica counts and pod details Other workloads (DaemonSets, StatefulSets, Static Pods) Standalone pods (if any) Pod-level details: status, node, restart count Has Alerts? Checks if any workloads have 0 ready pods Routes to appropriate action Send Telegram Alert (if alerts exist) Sends formatted alert message to Telegram Includes: Namespace information List of problematic workloads Full status report Save Report Saves the Markdown report to a file Filename format: k8s-report-YYYY-MM-DD-HHmmss.md Always executes, regardless of alert status Security Features Temporary kubectl**: Downloaded and used only during execution Temporary kubeconfig**: Written to /tmp/kubeconfig-<random>.yaml Automatic cleanup**: Kubeconfig file is deleted after each kubectl command No persistent credentials**: Nothing stored on disk between executions Alert Logic Alerts are triggered when any workload has zero ready pods: Deployments with readyReplicas < 1 DaemonSets with numberReady < 1 StatefulSets with readyReplicas < 1 Static Pods (Node-owned) with no ready instances Report Sections Deployments: All Deployment-managed pods (via ReplicaSets) Other Workloads: DaemonSets, StatefulSets, and Static Pods (kube-system components) Standalone Pods: Pods without recognized owners (rare) Alerts: Summary of workloads requiring attention KEY FEATURES Automatic kubectl management** - No pre-installation needed Multi-workload support** - Deployments, DaemonSets, StatefulSets, Static Pods Smart pod grouping** - Uses Kubernetes ownerReferences Conditional alerting** - Only notifies when issues detected Detailed reporting** - Pod-level status, node placement, restart counts Secure credential handling** - Temporary files, automatic cleanup Markdown format** - Easy to read and store TROUBLESHOOTING Issue: "Cannot read properties of undefined" Ensure both "Get Pods" and "Get Deployments" nodes execute successfully Check that kubectl can access your cluster with the provided kubeconfig Issue: No alerts when there should be Verify the namespace contains deployments or workloads Check that pods are actually not ready (use kubectl get pods -n <namespace>) Issue: Telegram message not sent Verify Telegram API credential is configured correctly Confirm chat ID is correct and the bot has permission to message you Check that the bot was started (send /start to the bot) Issue: kubectl download fails Check internet connectivity from n8n host Verify access to dl.k8s.io domain Consider pre-installing kubectl on the host and removing the download commands CUSTOMIZATION Change Alert Threshold Edit the Process & Generate Report node to change when alerts trigger: // Change from "< 1" to your desired threshold if (readyReplicas < 2) { // Alert if less than 2 ready pods alerts.push({...}); } Monitor Multiple Namespaces Duplicate the workflow for each namespace Or modify "Kubeconfig Setup" to loop through multiple namespaces Custom Report Format Edit the markdown generation in Process & Generate Report node to customize: Section order Information displayed Formatting style Additional Notification Channels Add nodes after "Has Alerts?" to send notifications via: Email (SMTP node) Slack (Slack node) Discord (Discord node) Webhook (HTTP Request node)