Smart email assistant: automate customer support with AI & Supabase
Intelligent Email Support System with Vector Database Overview This n8n workflow automates email support using AI and vector database technology to provide smart, context-aware responses. It seamlessly integrates email automation and document management, ensuring efficient customer support. 📌 System Components ✉️ Email Support System Email Monitoring & Classification Gmail trigger node monitoring inbox AI-powered email classification Intelligent routing (support vs non-support inquiries) AI Response Generation LangChain agent for response automation OpenAI integration for NLP-driven replies Vector-based knowledge retrieval Automated draft creation in Gmail Vector Database System Supabase vector store for document management OpenAI embeddings for vector conversion Fast and efficient similarity search 📂 Document Management System Google Drive Integration Monitors specific folders for new/updated files Automatic document processing Supports various file formats Document Processing Pipeline Auto file download & text extraction Smart text chunking for better indexing Embedding generation via OpenAI Storage in Supabase vector database 🔄 Workflow Processes 📧 Email Support Flow Monitor Gmail inbox for new emails AI classification of incoming messages Route support emails to AI response generator Perform vector similarity search for knowledge retrieval Generate personalized AI-driven response Create email drafts in Gmail 📁 Document Management Flow Monitor Google Drive for new/updated files Auto-download and process documents Clean up outdated vector entries for updated files Extract and split document text efficiently Generate OpenAI embeddings Store processed data in Supabase vector DB ⚙️ Setup Instructions 1️⃣ Prerequisites Supabase account & project OpenAI API key Gmail account with OAuth2 setup Google Drive API access n8n installation 2️⃣ Supabase Database Setup sql -- Create the vector extension create extension if not exists vector; -- Create the documents table create table documents ( id bigserial primary key, content text, metadata jsonb, embedding vector(1536) ); -- Create an index for similarity search create index on documents using ivfflat (embedding vectorcosineops) with (lists = 100); 3️⃣ Google Drive Setup Create & configure two monitored folders: RAG folder for new documents documents Assign correct folder permissions Add folder IDs to the workflow 4️⃣ Document Processing Configuration Set up triggers for file creation and file updates Configure text extraction: Define chunk size & overlap settings Set document metadata processing 🔍 Maintenance & Optimization 📌 Regular Tasks Monitor system performance Update the knowledge base regularly Review AI response quality Optimize vector search parameters Clean up outdated document embeddings ✅ Best Practices Document Organization Maintain structured folders & naming conventions Keep knowledge base content updated System Optimization Track AI classification accuracy Tune response times & chunk sizes Perform regular database maintenance 🛠️ Troubleshooting Email Issues Verify Gmail API credentials Check AI service uptime Monitor classification performance Document Processing Issues Ensure correct file permissions Validate extraction & embedding processes Debug vector database insertions
By BadrUSDT and TRC20 wallet tracker API workflow for n8n
Overview This n8n workflow is specifically designed to monitor USDT TRC20 transactions within a specified wallet. It utilizes the public blockchain database of TronScan, requiring no API authentication, to periodically check and process transaction data. This workflow is ideal for users who need an automated solution to track their TRC20 wallet transactions. Features Automated Tracking: Executes every 15 minutes to capture new transactions. Customizable Filters: Tailors the tracking based on specific parameters like transaction time and wallet addresses. Data Aggregation: Compiles transaction data into a single, structured list. Formatted Outputs: Presents transaction data in an organized and comprehensible format. Requirements N8N (self-hosted or cloud version) setup and operational. Basic understanding of N8N workflows and nodes. Setup and Configuration Import Workflow: Load the provided JSON workflow into your N8N instance. Configure Edit Fields Node: Enter your TRC20 wallet address in the 'Your Wallet Address' field. Adjust 'Number of transactions to retrieve per request' if necessary. (Default one set to 20 which is recommanded) TronScan Data Access: The workflow accesses TronScan's public blockchain data, so no additional configuration is required for API access. Schedule Trigger Node: Defaulted to trigger every 15 minutes. Modify as per your requirements. Test the Workflow: Execute the workflow manually to ensure everything is operating correctly. How it Works Schedule Trigger: Initiates the workflow at predetermined intervals. Edit Fields: Sets up the wallet address and transaction retrieval count. TronScan Data Retrieval: Gathers transaction data from the TRC20 wallet using TronScan's public database. Split Out & Filter: Processes and filters the transaction data. Final Results: Organizes and formats the required transaction data for review. Aggregate: Consolidates all records (items) into a one comprehensive list (item). Customization Modify the filter conditions and fields to suit your tracking needs. (for example you can higher or lower the number of time to filter or IN / OUT transactions - Default is 15m/IN) Adjust the schedule trigger frequency according to your preference (default is 15m). Best Practices Regularly test the workflow to ensure consistent performance. Stay updated with any changes to the structure of TronScan's public data that might affect the workflow. Contributing Your feedback and contributions are greatly appreciated. Feel free to adapt, modify, and share enhancements with the n8n community.
By NskhaAutomate GitHub PRs & JIRA updates from Git commit commands-single repo
This n8n template from Intuz delivers a complete and automated solution to streamline your development workflow for a single repository. By embedding specific keywords and a JIRA issue ID within your git commit commands, this workflow automatically creates a Pull Request in GitHub and simultaneously updates the corresponding JIRA ticket. This provides a complete, seamless integration that eliminates manual steps and keeps your project management perfectly in sync with your codebase. How it works This workflow acts as a powerful bridge between your Git repository and your project management tools, driven entirely by the structure of your commit messages. GitHub Webhook Trigger: The workflow starts when a developer pushes a new commit to a specified repository in GitHub. Parse Commit Message: A Code node extracts key information from the commit message: The JIRA Issue Key (e.g., FF-1196). The base branch for the PR (e.g., development). Action commands like [auto-pr] and [taskcompleted]. Conditional PR Creation: An IF node checks if the [auto-pr] command is present. If yes, it uses the GitHub node to automatically create a pull request from the developer's branch to the specified base branch. If no, this step is skipped, allowing for multiple commits before a PR is made. Conditional JIRA Update: Another IF node checks for the [taskcompleted] command. If yes, it uses the JIRA node to transition the corresponding issue to your "Done" status (e.g., "Task Completed" or "In Review"). If no, the JIRA issue remains in its current state, perfect for work-in-progress commits. How to Use: Quick Start Guide Click the "Use Template" button to import this workflow into your n8n instance. Configure the GitHub Trigger: Open the "GitHub Push Trigger" node. It will display a unique Webhook URL. Copy this URL. In your GitHub repository, go to Settings > Webhooks > Add webhook. Paste the URL into the Payload URL field. Set the Content type to application/json. Under "Which events would you like to trigger this webhook?", select Just the push event. Click Add webhook. Connect Your Accounts: GitHub: Select your GitHub API credential in the "Create Pull Request" node. JIRA : Select your JIRA API credential in the "Update JIRA Issue Status" node. Customize the JIRA Transition (Important): Open the "Update JIRA Issue Status" node. In the Transition parameter, you need to set the specific status you want to move the issue to (e.g., 'Done', 'Completed', 'In Review'). You can use the ID or the exact name of the transition from your JIRA project's workflow. Activate the Workflow: Save your changes and activate the workflow. You're ready to automate! Example Commit Message: git commit -m "FF-1196 Implement OAuth login [auto-pr,development,taskcompleted]" Key Requirements to Use Template An active n8n instance. A GitHub account with repository admin permissions to create webhooks. A JIRA Cloud account with permissions to update issues. Developers who can follow the specified git commit message format. Connect with us Website: https://www.intuz.com/services Email: getstarted@intuz.com LinkedIn: https://www.linkedin.com/company/intuz Get Started: https://n8n.partnerlinks.io/intuz For Custom Worflow Automation Click here- Get Started
By Intuz Predict disaster damage and coordinate property response with GPT-4, Google Sheets, Calendar and Gmail
How It Works This automated disaster response workflow streamlines emergency management by monitoring multiple alert sources and coordinating property protection teams. Designed for property managers, insurance companies, and emergency response organizations, it solves the critical challenge of rapidly identifying at-risk properties and deploying resources during disasters.The system continuously monitors weather, seismic, and flood alerts from authoritative sources. When threats are detected, it cross-references property databases to identify affected locations, calculates insurance exposure, and generates damage assessments using OpenAI's GPT-4. Teams receive automated maintenance schedules while property owners and insurers get instant email notifications with comprehensive reports. This eliminates manual monitoring, reduces response time from hours to minutes, and ensures no vulnerable properties are overlooked during emergencies. Setup Steps Configure alert fetch nodes with weather/seismic/flood API endpoints Connect property database credentials (specify database type) Add OpenAI API key for GPT-4 damage assessments Set up Gmail/SMTP credentials for owner and insurer notifications Customize insurance calculation formulas and team scheduling logic Prerequisites Weather/seismic/flood alert API access, property database (SQL/Sheets/Airtable) Use Cases Insurance companies automating claims preparation, property management firms protecting rental portfolios Customization Modify alert source APIs, adjust damage assessment prompts Benefits Reduces emergency response time by 90%, eliminates manual alert monitoring
By Cheng Siong Chin