Workflow Templates

Overview This automated workflow intelligently qualifies interior design leads, generates personalized client emails, and manages follow-up through a human-approval process. Built with n8n, Claude AI, Telegram approval, and Notion database integration. ⚠️ Hosting Options This template works with both n8n Cloud and self-hosted instances. Most nodes are native to n8n, making it cloud-compatible out of the box. What This Template Does Automated Lead Management Pipeline: Captures client intake form submissions from website or n8n forms AI-powered classification into HOT/WARM/COLD categories based on budget, project scope, and commitment indicators Generates personalized outreach emails tailored to each lead type Human approval workflow via Telegram for quality control Email revision capability for rejected drafts Automated client email delivery via Gmail Centralized lead tracking in Notion database Key Features ✅ Intelligent Lead Scoring: Analyzes 12+ data points including budget (AED), space count, project type, timeline, and style preferences ✅ Personalized Communication: AI-generated emails reference specific client details, demonstrating genuine understanding ✅ Quality Control: Human-in-the-loop approval via Telegram prevents errors before client contact ✅ Smart Routing: Different workflows for qualified leads (meeting invitations) vs. unqualified leads (respectful alternatives) ✅ Revision Loop: Rejected emails automatically route to revision agent for improvements ✅ Database Integration: All leads stored in Notion for pipeline tracking and analytics Use Cases Interior design firms managing high-volume lead intake Architecture practices with complex qualification criteria Home renovation companies prioritizing project value Any service business requiring budget-based lead scoring Sales teams needing approval workflows before client contact Prerequisites Required Accounts & API Keys: Anthropic Claude API - For AI classification and email generation Telegram Bot Token - For approval notifications Gmail Account - For sending client emails (or any SMTP provider) Notion Account - For lead database storage n8n Account - Cloud or self-hosted instance Technical Requirements: Basic understanding of n8n workflows Ability to create Telegram bots via BotFather Gmail app password or OAuth setup Notion database with appropriate properties Setup Instructions Step 1: Clone and Import Template Copy this template to your n8n instance (cloud or self-hosted) All nodes will appear as inactive - this is normal Step 2: Configure Form Trigger Open the Client Intake Form Trigger node Choose your trigger type: For n8n forms: Configure form fields matching the template structure For webhook: Copy webhook URL and integrate with your website form Required form fields: First Name, Second Name, Email, Contact Number Project Address, Project Type, Spaces Included Budget Range, Completion Date, Style Preferences Involvement Level, Previous Experience, Inspiration Links Step 3: Set Up Claude AI Credentials Obtain API key from https://console.anthropic.com In n8n: Create new credential → Anthropic → Paste API key Apply credential to these nodes: AI Lead Scoring Engine Personalized Client Outreach Email Generator Email Revision Agent Step 4: Configure Telegram Approval Bot Create bot via Telegram's @BotFather Copy bot token Get your Telegram Chat ID (use @userinfobot) In n8n: Create Telegram credential with bot token Configure Human-in-the-Loop Email Approval node: Add your Chat ID Customize approval message format if desired Step 5: Set Up Gmail Sending Enable 2-factor authentication on Gmail account Generate app password: Google Account → Security → App Passwords In n8n: Create Gmail credential using app password Configure Client Email Delivery node with sender details Step 6: Connect Notion Database Create Notion integration at https://www.notion.so/my-integrations Copy integration token Create database with these properties: Client Name (Title), Email (Email), Contact Number (Phone) Project Address (Text), Project Type (Multi-select) Spaces Included (Text), Budget (Select), Timeline (Date) Classification (Select: HOT/WARM/COLD), Confidence (Select) Estimated Value (Number), Status (Select) Share database with your integration In n8n: Add Notion credential → Paste token Configure Notion Lead Database Manager with database ID Step 7: Customize Classification Rules (Optional) Open AI Lead Scoring Engine node Review classification criteria in the prompt: HOT: 500k+ AED, full renovations, 2+ spaces WARM: 100k+ AED, 2+ spaces COLD: <100k AED OR single space Adjust thresholds to match your business requirements Modify currency if not using AED Step 8: Personalize Email Templates Open Personalized Client Outreach Email Generator node Customize: Company name and branding Signature placeholders ([Your Name], [Title], etc.) Tone and style preferences Alternative designer recommendations for COLD leads Step 9: Test the Workflow Activate the workflow Submit a test form with sample data Monitor each node execution in n8n Check Telegram for approval message Verify email delivery and Notion database entry Step 10: Set Up Error Handling (Recommended) Add error workflow trigger Configure notifications for failed executions Set up retry logic for API failures Workflow Node Breakdown 1. Client Intake Form Trigger Captures lead data from website forms or n8n native forms with all project details. 2. AI Lead Scoring Engine Analyzes intake data using structured logic: budget validation, space counting, and multi-factor evaluation. Returns HOT/WARM/COLD classification with confidence scores. 3. Lead Classification Router Routes leads into three priority workflows based on AI classification, optimizing resource allocation. 4. Sales Team Email Notifier Sends instant alerts to sales representatives with complete lead details and AI reasoning for internal tracking. 5. Personalized Client Outreach Email Generator AI-powered composer creating tailored responses demonstrating genuine understanding of client vision, adapted by lead type. 6. Latest Email Version Controller Captures most recent email output ensuring only final approved version proceeds to delivery. 7. Human-in-the-Loop Email Approval Telegram-based review checkpoint sending generated emails to team member for quality control before client delivery. 8. Approval Decision Router Evaluates reviewer's response, routing approved emails to client delivery or rejected emails to revision agent. 9. Email Revision Agent AI-powered editor refining rejected emails based on feedback while maintaining personalization and brand voice. 10. Client Email Delivery Sends final approved personalized emails demonstrating understanding of project vision with clear next steps. 11. Notion Lead Database Manager Records all potential clients with complete intake data, classification results, and tracking information for pipeline management. Customization Tips Adjust Classification Thresholds: Modify budget ranges and space requirements in the AI Lead Scoring Engine prompt to match your market and service level. Multi-Language Support: Update all AI agent prompts with instructions for your target language. Claude supports 100+ languages. Additional Routing: Add branches for special cases like urgent projects, VIP clients, or specific geographic regions. CRM Integration: Replace Notion with HubSpot, Salesforce, or Airtable using respective n8n nodes. SMS Notifications: Add Twilio node for immediate HOT lead alerts to mobile devices. Troubleshooting Issue: Telegram approval not received Verify bot token is correct Confirm chat ID matches your Telegram account Check bot is not blocked Issue: Claude API errors Verify API key validity and credits Check prompt length isn't exceeding token limits Review rate limits on your Anthropic plan Issue: Gmail not sending Confirm app password (not regular password) is used Check "Less secure app access" if using older method Verify daily sending limits not exceeded Issue: Notion database not updating Confirm integration has access to database Verify property names match exactly (case-sensitive) Check property types align with data being sent Template Metrics Execution Time**: ~30-45 seconds per lead (including AI processing) API Calls**: 2-3 Claude requests per lead (classification + email generation, +1 if revision) Cost Estimate**: ~$0.05-0.15 per lead processed (based on Claude API pricing) Support & Community n8n Community Forum**: https://community.n8n.io Template Issues**: Report bugs or suggest improvements via n8n template feedback Claude Documentation**: https://docs.anthropic.com Notion API Docs**: https://developers.notion.com License This template is provided as-is under MIT license. Modify and adapt freely for your business needs. Version: 1.0 Last Updated: October 2025 Compatibility: n8n v1.0+ (Cloud & Self-Hosted), Claude API v2024-10+

Overview Turn your cluttered inbox into a smart, autonomous assistant that categorizes emails, replies to leads, checks your calendar, and notifies you on Telegram—all without lifting a finger. This workflow is designed for a marketing agency, but can be adapted for any business. It classifies incoming emails into categories like Sales, Client Communication, Reports, Billing, and Other. If it detects a new lead or priority message, it routes the email to one of two agents: The Calendar Agent checks your availability in Google Calendar and drafts a consultation reply The Knowledge Agent answers FAQs using your business knowledge base (with Supabase embeddings) Both agents create draft email responses and send a Telegram alert so you're always in the loop. Who’s it for Founders and agency owners buried in emails Marketing teams handling lots of inbound leads Customer support managers automating Tier 1 replies Anyone who wants a cleaner, smarter inbox without hiring a VA How it works Gmail trigger watches for incoming emails Email content is passed to an AI classifier to apply a label (Sales, Client, Billing, etc.) If the message is a new inquiry or lead, it’s routed to: Calendar Agent → checks Google Calendar and drafts a reply with available slots Knowledge Agent → searches vector DB and drafts a helpful reply from documentation Both agents create a Gmail draft response and send a Telegram notification with summary Example use case > A lead emails you asking for a discovery call. > > ✅ Email is labeled "Sales" > ✅ AI Calendar Agent checks your Google Calendar > ✅ A reply is drafted offering free time slots > ✅ You get a Telegram ping: > "New lead: Abdul Mir. I checked your calendar and drafted a reply. Check your email!" How to set up Connect your Gmail and set up a trigger for new messages Train the AI classifier with example categories and emails Connect Google Calendar API for availability checks Upload your internal docs and sync to Supabase vector store Connect Telegram for alerts Customize AI prompts and escalation logic as needed Requirements Gmail integration OpenAI or Claude API (for classification + chat agents) Google Calendar API Supabase (or Pinecone, Weaviate) for RAG vector DB Telegram bot API key How to customize Add custom labels like “Recruiting,” “Investor,” or “Support” Replace Telegram with Slack or SMS alerts Add CRM sync to update lead status Escalate complicated replies to a human via task creation Add auto-send (instead of drafts) after review or based on confidence score

Android Feature Flag Cleanup Bot (GitLab + LaunchDarkly) This n8n automation detects unused (“dead”) feature flags in an Android Kotlin/Java codebase by comparing your GitLab repository code against LaunchDarkly’s feature flag list. It logs results in Google Sheets, creates Jira tickets for cleanup and sends Slack alerts automatically. Who’s it for Android engineering teams using Kotlin/Java. Teams managing feature flags in LaunchDarkly. DevOps/QA teams wanting to reduce technical debt from stale flags. How it works Weekly Trigger runs the process. GitLab Node fetches repository code. Regex Extraction finds all feature flags in code. LaunchDarkly API retrieves all configured flags. Comparison Logic marks flags as “dead” if unused in code and archived or off in production. Google Sheets stores flagged results. Jira creates a ticket for each dead flag. Slack notifies the team. How to set up Import JSON into n8n. Connect credentials for: GitLab OAuth2 Google Sheets Jira Slack webhook URL Update: GitLab repo details in the GitLab node. LaunchDarkly API key in HTTP Request node. Google Sheet ID in Google Sheets node. Jira project & issue type in Jira node. Slack message formatting in Slack node. Activate workflow. Requirements n8n** (self-hosted or cloud) GitLab repository with Kotlin/Java code LaunchDarkly account + API token Google Sheets API access Jira API access Slack incoming webhook How to customize Change regex pattern in “Detect flags” node if your flag naming convention differs. Adjust dead flag logic in “Find dead flags” node (e.g., treat test env separately). Modify Slack message to include more details (e.g., description from LaunchDarkly). Add email notifications for broader distribution. Add-ons Email Alerts** via Gmail/SMTP. GitHub / GitLab MR** to remove dead flags automatically. Confluence Integration** to document flag cleanup history. Use Case Examples Weekly automated cleanup alerts for large engineering teams. Maintaining clean feature flag lists in high-traffic apps. Compliance-driven projects requiring flag lifecycle tracking. Common troubleshooting | Issue | Possible Cause | Solution | | ------------------------------------ | --------------------------------------------- | -------------------------------------------------------- | | Workflow fails at GitLab node | Invalid repo path or missing OAuth scope | Update repo path & check GitLab OAuth permissions | | LaunchDarkly API request returns 401 | Invalid or expired API key | Generate a new API key in LaunchDarkly & update node | | Google Sheets node fails | Wrong Sheet ID or missing sharing permissions | Confirm Sheet ID and share with connected Google account | | Jira ticket not created | Missing required fields | Set project key, issue type, and summary in Jira node | | Slack alert not sent | Webhook URL invalid or revoked | Regenerate Slack webhook and update in node | Need Help? If you’d like, we can help set up and customize this workflow for your exact repo, flag rules and team notification preferences — including regex adjustments, extra reporting or adding automatic cleanup PRs. Contact our n8n automation team at WeblineIndia.

Who is it for This template is perfect for content creators, space enthusiasts, educators, and organizations who want to automatically generate and distribute engaging weekly space newsletters. It's especially useful for those who want to stay updated on space events without manual content creation. How it works This workflow automatically generates a comprehensive space newsletter every week by: Fetching the latest data from multiple NASA APIs (APOD, DONKI, NeoWS) Using AI to create an engaging newsletter from the raw data Creating a formatted document with the content Converting it to PDF format Distributing via email and archiving to your preferred platform Sending success notifications to your team Setup steps Get NASA API Key: Register at https://api.nasa.gov to get your API key (free) Configure OpenAI: Add your OpenAI credentials for content generation Set up Google Workspace: Connect Google Docs, Drive, and Gmail accounts Optional integrations: Configure Notion for archiving and Slack for notifications Customize schedule: Adjust the weekly trigger time to your preference Requirements NASA API key (free at api.nasa.gov) OpenAI API access Google Workspace account (Docs, Drive, Gmail) Optional: Notion and Slack accounts How to customize Modify the AI prompt to change the newsletter style and tone Adjust the date range for fetching space data Add or remove NASA API endpoints based on your interests Customize email recipients and notification channels Enable/disable the Notion archiving feature as needed

Google Drive to FTP Transfer Workflow - Setup Guide Overview This n8n workflow automatically transfers files from Google Drive to an FTP server on a scheduled basis. It includes comprehensive logging, email notifications, and error handling. Features Automated Scheduling**: Runs every 6 hours (customizable) Manual Trigger**: Webhook endpoint for on-demand transfers File Filtering**: Supports specific file types and size limits Comprehensive Logging**: Detailed transfer reports saved to Google Drive Email Notifications**: HTML reports sent after each run Error Handling**: Graceful handling of failed transfers Batch Processing**: Files processed individually to prevent rate limits Prerequisites Before setting up this workflow, ensure you have: n8n instance running (self-hosted or cloud) Google Drive account with files to transfer FTP server with upload permissions Email service for sending reports (SMTP) Step-by-Step Setup Instructions 1. Google Drive API Setup 1.1 Create Google Cloud Project Go to Google Cloud Console Create a new project or select existing one Enable the Google Drive API: Navigate to "APIs & Services" → "Library" Search for "Google Drive API" Click "Enable" 1.2 Create OAuth2 Credentials Go to "APIs & Services" → "Credentials" Click "Create Credentials" → "OAuth client ID" Configure consent screen if prompted Choose "Web application" as application type Add your n8n instance URL to authorized redirect URIs: https://your-n8n-instance.com/rest/oauth2-credential/callback Note down the Client ID and Client Secret 1.3 Configure n8n Credential In n8n, go to "Credentials" → "Add Credential" Select "Google Drive OAuth2 API" Enter your Client ID and Client Secret Complete OAuth flow by clicking "Connect my account" Set credential ID as: your-google-drive-credentials-id 2. FTP Server Setup 2.1 FTP Server Requirements Ensure FTP server is accessible from your n8n instance Verify you have upload permissions Note the server details: Host/IP address Port (usually 21 for FTP) Username and password Destination directory path 2.2 Configure n8n FTP Credential In n8n, go to "Credentials" → "Add Credential" Select "FTP" Enter your FTP server details: Host: your-ftp-server.com Port: 21 (or your custom port) Username: your-ftp-username Password: your-ftp-password Set credential ID as: your-ftp-credentials-id 3. Email Setup (SMTP) 3.1 Choose Email Provider Configure SMTP settings for one of these providers: Gmail**: smtp.gmail.com, port 587, use App Password Outlook**: smtp-mail.outlook.com, port 587 Custom SMTP**: Your organization's SMTP server 3.2 Configure n8n Email Credential In n8n, go to "Credentials" → "Add Credential" Select "SMTP" Enter your SMTP details: Host: smtp.gmail.com (or your provider) Port: 587 Security: STARTTLS Username: your-email@example.com Password: your-app-password Set credential ID as: your-email-credentials-id 4. Workflow Configuration 4.1 Import Workflow Copy the workflow JSON from the artifact above In n8n, click "Import from JSON" Paste the workflow JSON and import 4.2 Update Credential References Google Drive nodes: Verify credential ID matches your-google-drive-credentials-id FTP node: Verify credential ID matches your-ftp-credentials-id Email node: Verify credential ID matches your-email-credentials-id 4.3 Customize Parameters FTP Server Settings (Upload to FTP node) { "host": "your-ftp-server.com", // Replace with your FTP host "username": "your-ftp-username", // Replace with your FTP username "password": "your-ftp-password", // Replace with your FTP password "path": "/remote/directory/{{ $json.validFiles[$json.batchIndex].name }}", // Update destination path "port": 21 // Change if using different port } Email Settings (Send Report Email node) { "sendTo": "admin@yourcompany.com", // Replace with your email address "subject": "Google Drive to FTP File Transfer - Report" } File Filter Settings (Filter & Validate Files node) In the JavaScript code, update these settings: const transferNotes = { settings: { maxFileSizeMB: 50, // Change maximum file size allowedExtensions: [ // Add/remove allowed file types '.pdf', '.doc', '.docx', '.txt', '.jpg', '.png', '.zip', '.xlsx' ], autoDeleteAfterTransfer: false, // Set to true to delete from Drive after transfer verifyTransfer: true // Keep true for verification } }; Google Drive Notes Storage (Upload Notes to Drive node) { "parents": { "parentId": "your-notes-folder-id" // Replace with actual folder ID from Google Drive } } 5. Schedule Configuration 5.1 Modify Schedule Trigger In the "Schedule Trigger" node, adjust the interval: { "rule": { "interval": [ { "field": "hours", "hoursInterval": 6 // Change to desired interval (hours) } ] } } Alternative schedule options: Daily**: "field": "days", "daysInterval": 1 Weekly**: "field": "weeks", "weeksInterval": 1 Custom cron**: Use cron expression for complex schedules 5.2 Webhook Configuration The webhook trigger is available at: POST https://your-n8n-instance.com/webhook/webhook-transfer-status Use this for manual triggers or external integrations. 6. Testing and Validation 6.1 Test Connections Test Google Drive: Run "Get Drive Files" node manually Test FTP: Upload a test file using "Upload to FTP" node Test Email: Send a test email using "Send Report Email" node 6.2 Run Test Transfer Activate the workflow Click "Execute Workflow" to run manually Monitor execution in the workflow editor Check for any error messages or failed nodes 6.3 Verify Results FTP Server**: Confirm files appear in destination directory Email**: Check you receive the transfer report Google Drive**: Verify transfer notes are saved to specified folder 7. Monitoring and Maintenance 7.1 Workflow Monitoring Execution History**: Review past runs in n8n interface Error Logs**: Check failed executions for issues Performance**: Monitor execution times and resource usage 7.2 Regular Maintenance Credential Renewal**: Google OAuth tokens may need periodic renewal Storage Cleanup**: Consider archiving old transfer notes Performance Tuning**: Adjust batch sizes or schedules based on usage 8. Troubleshooting 8.1 Common Issues Google Drive Authentication Errors: Verify OAuth2 credentials are correctly configured Check if Google Drive API is enabled Ensure redirect URI matches n8n instance URL FTP Connection Failures: Verify FTP server credentials and connectivity Check firewall settings allow FTP connections Confirm destination directory exists and has write permissions Email Delivery Issues: Verify SMTP credentials and server settings Check if email provider requires app-specific passwords Ensure sender email is authorized File Transfer Failures: Check file size limits in filter settings Verify allowed file extensions include your file types Monitor FTP server disk space 8.2 Debug Mode Enable debug mode by: Adding console.log statements in code nodes Using "Execute Workflow" with step-by-step execution Checking node outputs for data validation 9. Advanced Customizations 9.1 Additional File Filters Add custom filtering logic in the "Filter & Validate Files" node: // Example: Filter by modification date const isRecentFile = new Date(file.modifiedTime) > new Date(Date.now() - 7 * 24 * 60 * 60 * 1000); // Last 7 days // Example: Filter by folder location const isInSpecificFolder = file.parents && file.parents.includes('specific-folder-id'); 9.2 Enhanced Reporting Customize the email report template in "Send Report Email" node: 📊 File Transfer Report Summary Date: {{ new Date().toLocaleString('en-US') }} Success Rate: {{ Math.round((successfulTransfers / totalFiles) * 100) }}% 9.3 Integration with Other Services Add nodes to integrate with: Slack**: Send notifications to team channels Discord**: Post updates to Discord servers Webhook**: Trigger other workflows or systems Database**: Log transfers to MySQL, PostgreSQL, etc. 10. Security Considerations 10.1 Credential Security Use environment variables for sensitive data Regularly rotate FTP and email passwords Implement least-privilege access for service accounts 10.2 Network Security Use SFTP instead of FTP when possible Implement VPN connections for sensitive transfers Monitor network traffic for unusual patterns 10.3 Data Privacy Ensure compliance with data protection regulations Implement data retention policies for transfer logs Consider encryption for sensitive file transfers Support and Resources Documentation Links n8n Documentation Google Drive API Documentation n8n Community Forum Getting Help If you encounter issues: Check the troubleshooting section above Review n8n execution logs for error details Search the n8n community forum for similar issues Create a support ticket with detailed error information Note: Replace all placeholder values (URLs, credentials, IDs) with your actual configuration before running the workflow.

AI-Powered Wealth Management: Automated Client Portfolio Update & Advisor Approval This n8n workflow automates the transition from raw financial trade data to professional client communication. It monitors a Google Sheet for portfolio changes, uses Gemini AI to draft a personalized, risk-aware explanation email and sends it to an advisor via Slack for manual approval. Once approved, the email is sent automatically via Gmail and the source spreadsheet is updated to "Completed." Quick Start Implementation Import the JSON file into your n8n account. Connect Credentials: Set up OAuth2 for Google Sheets, Gmail, Slack and Google Gemini (AI). Sheet Setup: Ensure your Google Sheet has columns for Client_ID, Client_Name, Trades_Made and Trigger_Status. Configure Approval: Update the Slack node with your specific Member ID or Channel ID. Test: Change a row's Trigger_Status in your sheet to see the AI draft appear in Slack. What It Does In the high-stakes world of wealth management, keeping clients informed is vital but time-consuming. This workflow bridges the gap between technical data and human relationship management. It acts as an "AI Assistant" that watches your portfolio database (Google Sheets) for any new trades. Instead of sending a cold list of tickers, it passes that data to an AI model to write a warm, professional narrative. The workflow prioritizes safety through a Human-in-the-Loop design. Before any client sees the AI-generated content, the draft is sent to a dedicated Slack channel. The advisor can review the logic and tone, then simply click "Approve" or "Reject" via interactive buttons. This ensures that the final communication always meets the firm's compliance and quality standards. Finally, the workflow handles the "paperwork." If approved, it sends the email through Gmail and updates the spreadsheet status to "Completed." If rejected, it flags the record for "Manual Review," ensuring no client request is ever lost in the shuffle. Who It's For Wealth Managers & Financial Advisors** who want to scale personalized client touchpoints. Investment Operations Teams** looking to reduce manual drafting time. FinTech Startups** needing an automated communication layer for their portfolio management tools. Customer Success Teams** in the financial sector who handle high-volume account updates. Requirements to use this workflow n8n account. Google Workspace Account**: For Google Sheets (database) and Gmail (messaging). Slack Workspace**: To receive and action the approval notifications. Google Gemini API Key**: To power the AI drafting engine. Credential Permissions**: The n8n instance must have "Read/Write" access to your specific Google Sheet. How It Works & Set Up 1. Trigger & Data Ingestion The workflow starts with the Google Sheets Trigger node. It is configured to "poll" your sheet every minute. It specifically watches the Trigger_Status column for any updates. Setup: Select your Spreadsheet and the specific Sheet (tab) name. Ensure "Columns to Watch" is set to your status column. 2. Logic & Contextual Enrichment The data then moves through a Code Node that parses the stringified trade data (like tickers and amounts) into a format the AI can read. Setup: The workflow uses "Mock" nodes for Client Risk Profile and Market Context. For production, you should replace these with a "Google Sheets: Get Row" node or an "HTTP Request" node to pull the real risk profile of the client and live market news. 3. AI Drafting The AI: Draft Client Email node uses the Gemini model to combine the client’s name, their risk level, current market volatility and the specific trades made. It follows a strict prompt to ensure the email is professional and formatted correctly. 4. The Approval Gate The Slack node sends the draft to the advisor. The message includes two dynamic links: Approve and Reject. The Wait Node: After sending the Slack message, the workflow "pauses." It will wait for the advisor to click one of those links before moving to the next step. 5. Execution Depending on the button clicked: Approve: The **Switch Node routes the flow to Gmail, sends the message to the client and updates the Sheet status to "Completed." Reject**: The flow alerts the advisor in Slack that the draft was discarded and updates the Sheet to "Needs Manual Review." How To Customize Nodes AI Persona**: Edit the "AI: Draft Client Email" node's prompt to change the tone (e.g., make it more "Executive" or "Friendly"). Wait Time: Open the **Wait: Advisor Action node to change the timeout. If an advisor doesn't respond within 2 days (default), you can set the workflow to automatically reject or notify a manager. Dynamic Email: In the **Gmail node, replace the hardcoded "Send To" address with an expression like {{ $json.Client_Email }} to ensure it goes to the correct person. Add‑ons News API Integration**: Replace the "Mock: Market Context" node with a live news feed to provide real-time market insights in the email. PDF Report Attachment**: Add a node to generate a PDF summary of the trades and attach it to the Gmail sent to the client. CRM Sync**: Add a Salesforce or HubSpot node to log the communication in the client's activity history automatically. Use Case Examples Standard Rebalancing**: Notifying clients when their portfolio is adjusted to stay within risk targets. Market Volatility Alerts**: Proactively explaining why trades were made during a market dip. Tax-Loss Harvesting**: Explaining the benefits of specific trades made for tax optimization at year-end. New Product Onboarding**: Introducing a client to a new asset class added to their portfolio. Compliance Notifications**: Ensuring all mandated trade disclosures are sent and logged instantly. Troubleshooting Guide | Issue | Possible Cause | Solution | | :--- | :--- | :--- | | Workflow doesn't trigger | Trigger column name mismatch. | Ensure the column name in the "Trigger" node matches exactly with the Google Sheet. | | AI Draft is nonsensical | Input data (Trades) is empty. | Check that the Trades_Made column in your sheet contains valid JSON or text. | | Slack links don't work | n8n Webhook URL is not public. | Ensure your n8n instance is accessible from the internet (using a tunnel or static IP). | | Gmail fails to send | Credential permissions. | Re-authenticate your Gmail OAuth2 and ensure "Send" permissions are granted. | Need Help? Setting up automated financial workflows can be complex. If you need a hand configuring your AI prompts, connecting your live market data or building more advanced "Human-in-the-Loop" systems, we are here to help! Contact WeblineIndia to customize this workflow or build a custom automation solution tailored to your business needs.

Description A comprehensive real estate chatbot automation system that handles customer inquiries, property searches, and appointment scheduling through intelligent conversation flows and email processing. How it works? This template creates an end-to-end real estate automation system that handles customer inquiries from initial contact through appointment booking. 1. Customer Entry Point Webhook receives customer messages from chat interface Link detection checks if customer shared property URLs Smart routing - if property link found, fetch details immediately; otherwise proceed to chat 2. AI Content Processing Content filter (PRIORITY) - blocks non-real estate queries upfront Information extraction - scans messages for personal details and property requirements Human handoff detection - identifies requests for live agent assistance 3. Data Collection Phase Sequential gathering: Personal info (name → phone → email) then property needs Smart validation - phone format, email structure, budget parsing No redundancy - never asks for information already provided PostgreSQL storage - saves customer data and conversation memory 4. Property Search & Matching Database query filters properties by type, location, budget, availability Image enhancement - fetches property photos from media storage Results ranking - returns top 5 matches sorted by price 5. AI Response Generation GPT-4 formatting creates engaging, professional property listings Visual enhancement - includes property images and key details Personalized tone - acknowledges customer preferences 6. Appointment Automation Gmail monitoring - checks for appointment confirmations every hour Calendar integration - creates, updates, deletes appointments automatically Smart scheduling - checks availability, suggests alternatives for conflicts Email responses - sends confirmations and follow-ups Intelligence Features Context Awareness Remembers conversation history across sessions Builds complete customer profile progressively Maintains property preferences throughout interaction Smart Extraction Recognizes property types: HDB, Condo, Apartment Parses locations and MRT preferences automatically Handles various budget formats (SGD 2,500, $2500, etc.) Identifies timeline requirements and citizenship status Professional Handoffs Detects human agent requests with keyword matching Collects complete customer context before transfer Sends structured handoff emails with all requirements Ensures smooth transition to live agents Technical Components AI Models OpenAI GPT-4 - Main conversation handling and response formatting GPT-4 Mini - Appointment processing and email management LangChain Memory - Conversation context retention Database Integration PostgreSQL - Customer data, property listings, conversation history Property search with multi-criteria filtering Media storage integration for property images Communication Channels Webhook API - Primary chat interface Gmail integration - Appointment confirmations and notifications Google Calendar - Automated scheduling and availability checking Setup Requirements Configure database - PostgreSQL with property and customer tables Set up integrations - Gmail, Google Calendar, OpenAI API Customize prompts - Adjust AI responses for your brand Test workflow - Verify end-to-end functionality Monitor performance - Track conversation success rates The system is designed to handle the complete customer journey from initial inquiry to scheduled property viewing, with intelligent automation reducing manual work while maintaining high service quality.

How it works This workflow triggers when a HubSpot deal stage changes to Closed Won and automatically generates an invoice. It collects deal and contact data, builds a styled invoice, converts it into a PDF, and sends it to the client. The system logs all invoices and alerts the team, then monitors payment status with automated reminders. If payment is delayed, it escalates the issue and handles errors separately. Step-by-step Trigger and data collection** HubSpot - Deal Trigger – Starts workflow on deal stage change. IF - Is Deal Closed Won? – Filters only Closed Won deals. HTTP - Get Deal Details – Fetches deal information. HTTP - Get Deal Associations – Retrieves linked contacts. Code - Extract Contact ID – Extracts and formats data. HTTP - Get Contact Details – Gets customer details. Invoice generation** Code - Build Invoice + HTML – Creates invoice data and HTML layout. Send and store invoice** HTTP - Generate PDF – Converts HTML into PDF. Google Sheets - Log Invoice – Stores invoice records. Notion - Create Invoice Record – Tracks invoice internally. Gmail - Send Invoice Email – Sends invoice to client. Slack - Invoice Sent Alert – Notifies team. Payment tracking and follow-up** Wait - 7 Day Payment Window – Waits before checking payment. HTTP - Recheck Deal Stage – Checks payment status. IF - Payment Received? – Branches based on payment. Gmail - Follow-up Email #1 – Sends reminder if unpaid. Wait - 5 More Days – Adds extra delay. HTTP - Final Payment Check – Verifies final status. Slack - Payment Confirmed – Confirms successful payment. Escalation handling** IF - Still Unpaid? (Escalate) – Detects overdue invoices. Slack - Escalation Alert – Alerts team for action. Notion - Flag as Overdue – Updates record status. Slack - Late Payment Confirmed – Handles delayed payments. Error handling (separate flow)** Error Trigger – Captures workflow failures. Slack - Workflow Error Alert – Sends error notification. Why use this? Fully automates invoicing from deal closure to payment tracking Reduces manual billing work and human errors Improves payment collection with automated reminders Provides clear visibility with logs and team alerts Ensures reliability with built-in error monitoring

📚In the social and behavioral sciences (e.g., psychology, sociology, economics, management), researchers and students often need to normalize academic paper metadata and extract variables before any literature review or meta-analysis. 🧩This workflow automates the busywork. Using an LLM, it processes CSV/XLSX/XLS files (exported from WoS, Scopus, EndNote, Zotero, or your own spreadsheets) into normalized metadata and extracted variables, and writes a neat table to Google Sheets. 🔗 Example Google Sheet: click me 👥 Who is this for? 🎓 Undergraduate and graduate students or researchers in soft-science fields (psychology, sociology, economics, business) ⏱️ People who don’t have time to read full papers and need quick overviews 📊 Anyone who wants to automate academic paper metadata normalization and variable extraction to speed up a literature review ⚙️ How it works 📤 Upload an academic paper file (CSV/XLSX/XLS) in chat. 📑 The workflow creates a Google Sheets spreadsheet with two tabs: Checkpoint and FinalResult. 🔎 A structured-output LLM normalizes core metadata (title, abstract, authors, publication date, source) from the uploaded file and writes it to Checkpoint; 📧 a Gmail notification is sent when finished. 🧪 A second structured-output LLM uses the metadata above to extract variables (Independent Variable, Dependent Variable) and writes them to FinalResult; 📧 you’ll get a second Gmail notification when done. 🛠️ How to set up 🔑 Credentials Google Sheets OAuth2** (read/write) Gmail OAuth2** (send notifications) Google Gemini (or any LLM you prefer)** 🚀 Quick start Connect Google Sheets, Gmail, and Gemini (or your LLM) credentials. Open File Upload Trigger → upload your CSV/XLSX/XLS file and type a name in chat (used as the Google Sheets spreadsheet title). Watch your inbox for status emails and open the Google Sheets spreadsheet to review Checkpoint and FinalResult. 🎛 Customization 🗂️ Journal lists: Edit the Journal Rank Classifier code node to add/remove titles. The default list is for business/management journals—swap it for a list from your own field. 🔔 Notifications: Replace Gmail with Slack, Teams, or any channel you prefer. 🧠 LLM outputs: Need different metadata or extracted data? Edit the LLM’s system prompt and Structured Output Parser. 📝 Note 📝 Make sure your file includes abstracts. If the academic paper data you upload doesn’t contain an abstract, the extracted results will be far less useful. 🧩 CSV yields no items? Encoding mismatches can break the workflow. If this happens, convert the CSV to .xls or .xlsx and try again. 📩 Help Contact: owenlzyxg@gmail.com

WORKFLOW OVERVIEW This workflow is an AI-powered business intelligence agent designed for founders and business owners. It automatically collects key business metrics, calculates performance KPIs, applies decision logic, uses AI reasoning, and sends clear, actionable notifications — without dashboards or manual reports. Key Features: ✅ Aggregates multiple data sources (MSSQL, Google Analytics, Google Sheets) ✅ Calculates critical KPIs: ROAS, CAC, Revenue & User Growth ✅ Applies rule-based decision logic for business risk and opportunity detection ✅ AI-powered reasoning: summarizes insights and recommends actions ✅ Multi-channel notifications: Email, WhatsApp, Slack, Telegram ✅ Fully automated daily execution via Cron trigger ✅ Enterprise-ready: error handling, structured data, KPI validation Setup & Requirements: API access to data sources (MSSQL, Google Analytics, Google Sheets) OpenAI or Google Gemini API for AI reasoning Messaging integration: Gmail, Twilio (WhatsApp), Slack, Telegram Workflow Flow: Cron Trigger – runs daily at a chosen time Data Collection – revenue, users, marketing spend, website analytics Merge Node – combines all data sources Function Node – consolidates into a single JSON object KPI Calculation – calculates ROAS, CAC, growth rates Business Logic Engine – identifies risks and opportunities AI Reasoning Agent – summarizes insights, suggests actions Notification Formatter – builds founder-friendly message Notification Delivery – sends via WhatsApp, Email, Slack, or Telegram Example Data Formation These data below Getting from all different channels. `{ "revenue": 4290, "registeredUsers": 20, "totalUsers": 3, "adSpend": 800 }` Applies rule-based logic to detect potential risks or opportunities `{ "ROAS": 5.36, "CAC": 40, "agentStatus": "normal", "agentPriority": "low", "insights": ["Marketing campaigns are performing very well"] }` Workflow Highlights Fully automated, runs daily without human intervention Integrates multiple business data sources Converts raw data into KPIs for actionable insight Applies both rule-based logic and AI reasoning Generates concise, human-friendly notifications Sending notification to different channels.

Overview This workflow turns audio attachments you receive by Gmail into Japanese transcripts and structured AI summaries, then saves everything to Google Drive and Google Sheets while notifying you via Gmail and Slack. Every time an email with a voice recording arrives, the audio is stored in a dated folder, fully transcribed in Japanese, summarized into clear meeting-style points, and logged so you can quickly review and search later. Audio Email to Japanese Transcr… Audio Email to Japanese Transcript with AI Summary & Multi-Channel Notification Who this is for People who get voice memos or meeting recordings as email attachments Teams that want clear Japanese transcripts plus action-item summaries from calls Anyone who wants audio notes automatically archived and searchable in Drive/Sheets How it works Trigger: New Gmail with audio attachment A Gmail Trigger watches your inbox, downloads attachments for each new email, and passes them into the workflow. Split & filter attachments A Code node splits the email into one item per attachment and normalizes the binary data to binary.data. A Filter node keeps only audio files (mp3, wav, m4a, ogg) and discards everything else. Create date-based Drive folder & upload audio A Code node builds a YYYY/MM folder path from the current date. A Google Drive node creates that folder (if it doesn’t exist) under your chosen parent folder. A Merge node combines folder info with file info, and the audio file is uploaded into that folder so all recordings are organized by year/month. Transcribe audio to Japanese text An HTTP Request node calls the OpenAI Audio Transcriptions API (gpt-4o-transcribe) with the audio file. The prompt tells the model to produce a verbatim Japanese transcript (no summarization, no guessing), returned as plain text. Generate structured AI summary The transcript is sent to an OpenAI Chat node (gpt-4o), which outputs JSON with: title: short Japanese title for the recording points: key discussion points (array) decisions: decisions made (array) actionItems: action items with owner/deadline (array) A Set node then formats this JSON into a Markdown summary (summaryContent) with sections for 要点 / 決定事項 / アクションアイテム. Save transcript & summary files to Drive The transcript text is converted into a .txt file and uploaded to the same YYYY/MM folder. The Markdown summary is converted into a .md file (e.g. xxx_summary.md) and uploaded as well. Each file is then shared in Drive so you have accessible web links to both transcript and summary. Log to Google Sheets A Code node collects the email subject, file name, full transcript, formatted summary, and Drive links into one JSON object. A Google Sheets node appends a new row with timestamp, subject, summary, transcript, and link so you get a running log of all processed audios. Notify via Gmail & Slack Finally, the workflow: Sends a Gmail message back to the original sender with the meeting summary and links Posts a Slack notification in your chosen channel, including subject, file name, summary text, and Drive link How to set up Connect your Gmail, Google Drive, Google Sheets, Slack, and OpenAI credentials in the respective nodes. In the Gmail Trigger, narrow the scope if needed (e.g. specific label, sender, or inbox). In the Drive nodes, set the parent folder where you want the YYYY/MM subfolders to be created. In the Google Sheets node, point to your own spreadsheet and sheet name. In the Slack node, select the channel where reminders should be posted. Make sure your OpenAI credentials have access to both audio transcription and chat endpoints. Customization ideas Filter by sender, subject keyword, or label so only certain emails are processed. Change the folder structure (e.g. ProjectName/YYYY/MM or YYYY/MM/DD) in the folder-path Code node. Adjust the transcription prompt (e.g. allow light punctuation clean-up, use another language). Modify the summary format or add extra fields (e.g. meeting participants, project name) in the AI prompt and Markdown template. Send notifications to other tools: add branches for Notion, LINE, Teams, or additional Slack channels.

Description This workflow is designed to evaluate newly added CVs for Diversity, Equity, and Inclusion (DEI) eligibility. It automatically ingests CVs from Google Drive, extracts key fields, analyzes them with Azure OpenAI, logs structured DEI outcomes in Google Sheets, and sends a concise DEI-focused summary email to the hiring manager. The entire flow prioritizes consistent, auditable DEI checks and controlled logic paths. What This Template Does Watches Google Drive for new CV files to trigger DEI evaluation. Downloads and extracts text/structured fields from PDF CVs. Assesses DEI eligibility using Azure OpenAI, following defined criteria and prompts. Appends DEI results (eligible/not eligible, rationale, confidence) to Google Sheets for tracking. Generates and sends a DEI-focused summary email to the hiring manager for review. Key Benefits Standardized DEI screening to support equitable hiring decisions. Centralized, structured logging in Sheets for transparency and audits. Automated DEI summaries for faster, consistent manager review. Reliable routing with true/false logic to enforce DEI evaluation steps. Features Google Drive trigger (fileCreated) for CV intake tied to DEI checks. PDF extraction mapped to fields relevant for DEI evaluation. Azure OpenAI Chat Model prompts tuned for DEI criteria and rationale. Google Sheets append with eligibility status, notes, and timestamps. Email node that delivers DEI summaries and next-step guidance. Logic branching (true/false) to control DEI evaluation and notifications. Requirements n8n instance (cloud or self-hosted). Google Drive access to the CV intake folder. Google Sheets access for DEI results logging. Azure OpenAI access and configured prompts reflecting DEI criteria. Email node credentials to send DEI summaries to managers. Step-by-Step Setup Instructions Connect Google Drive and select the CV folder for the fileCreated trigger. Configure the Download CV and Extract From PDF nodes to capture fields needed for DEI checks. Add Azure OpenAI credentials and set DEI-specific prompts (criteria, rationale, confidence). Connect Google Sheets and select the target sheet; map columns for status, rationale, and timestamps. Configure the Email to Manager node with a DEI-focused subject and template. Test with sample CVs, verify sheet entries and email content, then enable the workflow. DEI-Focused Best Practices Clarify DEI criteria and document them in your prompt and sheet schema. Avoid including sensitive PII in emails; store only necessary fields for DEI decisions. Use n8n Credentials; never hardcode API keys or private data. Maintain an audit trail (timestamps, model version, prompt version, decision rationale). Periodically review prompts and sheet schema to align with policy updates.