by Muhammad Bello
Description This n8n template automates prospect research and personalized follow-up writing right after a sales call is booked. It gathers company background, tech stack, and updates; suggests relevant solutions; and then drafts a handcrafted email, subject line, and SMS, all saved back into Google Sheets. Benefits Always show up to calls with prepared context. Ensure no follow-up slips through the cracks. Keep all notes, research, and outreach in a single system of record. Scale personalized outreach without losing the human touch. Use cases Prep for sales calls with richer prospect context. Save hours writing personal follow-ups. Keep sales records neatly in one shared sheet. Requirements Google Sheets with: Meeting Data → prospect info + enrichment fields Success Stories → testimonials (company, industry, results, solution used) Tavily API key OpenAI API key (GPT-4.1 or later recommended) n8n account with Google Sheets + LangChain enabled Google Sheets Template You’ll need two sheets inside one Google Spreadsheet: 1. Meeting Data (input + output) Columns: Name Email Company Website Job Title Meeting Date Company Overview (AI-filled) Tech Stack (AI-filled) Company Updates (AI-filled) Primary Solution (AI-filled) Solution 2 (AI-filled) Solution 3 (AI-filled) Email Subject (AI-filled) Follow-up Email (AI-filled) Follow-up SMS (AI-filled) 2. Success Stories (for testimonials) Columns: Company Industry Results Solution Used You can copy this structure into a fresh Google Spreadsheet before starting. How it works Trigger → Pulls new rows from Google Sheets (or connects to your booking system). Research Agent → Uses Tavily for company overview, tech stack, and updates. Product Suggestions → Pulls from Product List sheet to propose 3 tailored solutions. Save Research → Updates the row with the six research fields. Sales Writing Assistant → Drafts subject, email, and SMS using context + testimonials. Update Sheet → Writes final outputs (subject, email, SMS) into Google Sheets. Setup Steps Prepare Google Sheets Create a new spreadsheet with the Meeting Data and Success Stories tabs. Add the required columns (see template above). Fill in at least one success story for the workflow to use. Connect Google Sheets in n8n Add Google Sheets credentials under Settings → Credentials. Make sure n8n has access to your spreadsheet. Add API Keys In n8n, create credentials for OpenAI (GPT-4.1 or later). Create credentials for Tavily. Import the workflow Load the JSON file (this template) into n8n. Replace any placeholder spreadsheet IDs with your own. Map the correct sheet/tab names. Test the Research Agent Run the workflow manually. Check that Company Overview, Tech Stack, and Company Updates populate. Test the Writing Assistant Ensure the workflow uses at least one testimonial from Success Stories. Run it again and confirm Email Subject, Follow-up Email, and SMS are written. Automate Replace the Manual Trigger with your preferred trigger: Google Calendar / Calendly → Google Sheets CRM → Google Sheets Directly from n8n integrations Customization This workflow is designed as a flexible foundation. Here are ways to adapt it: Change AI prompts** Update the Research Agent prompt to focus on specific industries or data points. Edit the Sales Writing Assistant to match your tone of voice. Swap success stories** Add more detailed case studies to the Success Stories sheet for stronger personalization. Add integrations** Send follow-up emails automatically with Gmail or Outlook nodes. Push SMS directly via Twilio. Sync enriched data into HubSpot, Salesforce, or Notion. Error handling** Add retry logic for API calls. Include a notification node (Slack/Email) if the workflow fails. Tips & Troubleshooting If research doesn’t update → confirm Email is the matching column in your Update Sheet nodes. If follow-up copy is blank → ensure at least one testimonial exists in Success Stories. Use Debug Mode to inspect AI Agent or Sales Writing Assistant outputs.
by Alok Kumar
Multi-Level Document Approval & Audit Workflow This workflow automates a document approval process using Supabase and Gmail. Who it’s for Teams that need structured multi-level document approvals. Companies managing policies, contracts, or proposals. Medical document need multiple lavel of review and approval. How it works Form Trigger – A user submits a document via the form. Supabase Integration – The document is saved in the documents table. Supabase Storage – The document is saved in the bucket. Workflow Levels – Fetches the correct approval level from workflow_levels. Assign Approvers – Matches approvers by role from the users table. Approval Record – Creates an approvals record with a unique token and expiry. Email Notification – Sends an email with Approve / Reject links. Audit Logs – Records every approval request in audit_logs. Repeat - repeat the flow till all the aproval level is comepted How to set up Configure your Supabase credentials. Create tables as per data model given. Create a storage bucket in Supabase Storage. Connect your Gmail account. Adjust approval expiry time (48h default). Deploy and test via the Form Trigger. Customization Add multiple approval levels by chaining workflow_levels. Replace Gmail with Slack, Teams, or another notification channel. Adjust audit logging for compliance needs. Update the endpoint http://localhost:5678/webhook-test/ based on instance and env (remove test if you run in prod) Update the bucket name. Important steps 1. Form Submit Triggered when by submiting form Captures form parameters: Title (Document Title) Description (Document Description) file (Document need for approval) 2. Webhook Entry Point Triggered when an approver clicks the Approve or Reject link in email. Captures query parameters: token (approval token) decision (approved/rejected) 3. Approval Data Retrieval & Update Fetch approval record from Supabase (approvals) using token. Update approval status: Approved → moves to next workflow level or final approval. Rejected → document marked as rejected immediately. Records acted_at timestamp. 4. Decision Check IF Node* checks whether the decision is *approved* or *rejected**. Reject Path* → Update document status to *Rejected** in documents. Approve Path** → Continue workflow level progression. 5. Workflow Level Progression Fetch details of the current workflow level. Identify the next level (workflow_levels) based on level_number. ✅ If Next Level Exists: Retrieve approvers by role_id. Generate unique approval tokens. Create new approval records in approvals. Send email notifications with approval/reject links. ❌ If No Next Level (Last Level): Update document status to Approved in documents. 6. Audit Logging Every approval action is logged into audit_logs table: document_id action (e.g., approval_sent, approved, rejected) actor_email (system/approver) details (workflow level, role info, etc.) 📨 Email Template Approval request email includes decision links: Please review the document: ✅ Approve | ❌ Reject Happy Automating! 🚀
by Roshan Ramani
Who's it for This template is designed for professionals, entrepreneurs, and busy individuals who receive high volumes of emails and want to automate their email management. Perfect for freelancers, small business owners, project managers, and anyone who struggles with email overload and wants AI-powered assistance for prioritizing and responding to messages. How it works The workflow creates an intelligent email processing system that monitors your Gmail inbox in real-time and categorizes every incoming email using Google Gemini AI. Here's what happens: Real-time Processing: Every minute, the system checks for new emails and uses AI to classify them into three categories: Category 0 (Needs Reply)**: Questions, meeting requests, urgent business matters Category 1 (Important Notifications)**: Bills, confirmations, system alerts, order updates Category 2 (Spam/Unimportant)**: Marketing emails, newsletters, promotional content Smart Response Generation: For emails requiring replies, AI generates professional responses and sends them to your Telegram for approval. Once approved, the reply is automatically sent from your Gmail account. Instant Notifications: Important emails get summarized and sent as quick Telegram notifications so you stay informed without checking email constantly. Daily Email Digest: Every morning at 8 AM, you receive a comprehensive summary of the previous day's emails, including action items, issues requiring attention, and follow-up tasks. How to set up Step 1: Gmail Configuration Connect your Gmail account using OAuth2 authentication Ensure Gmail API access is enabled in your Google Cloud Console Step 2: Telegram Setup Create a new Telegram bot using @BotFather Get your bot token and personal chat ID Configure the Telegram credentials in n8n Step 3: AI Configuration Set up Google Cloud account with Gemini API access Create API credentials for Google Palm/Gemini Add the credentials to your n8n instance Step 4: Workflow Customization Update all Telegram chat IDs with your personal chat ID Configure the daily trigger schedule according to your timezone Test the workflow with sample emails Requirements Gmail account** with API access enabled Telegram bot** and personal chat ID Google Cloud account** with Gemini API access n8n instance** (self-hosted or cloud) All sensitive information like API keys, chat IDs, and email addresses should be configured using n8n's credential system rather than hardcoding them in the workflow. How to customize the workflow Modify Classification Logic Edit the AI Email Classifier node's system prompt to adjust how emails are categorized based on your specific industry or email patterns. Adjust Scheduling Change the Daily 8AM Trigger to your preferred time zone and schedule for receiving email summaries. Personalize Response Style Customize the AI reply generator's system prompt to match your communication style, tone, and professional voice. Enhance Filtering Add additional filtering logic to process emails from specific senders, domains, or with particular keywords differently. Extend Notifications Configure multiple Telegram chats for different types of notifications (personal vs work) or add other messaging platforms. Security Best Practices Use n8n environment variables for sensitive configuration Store all credentials securely using n8n's credential management Avoid hardcoding personal information in node parameters Test thoroughly in a development environment before production use The workflow is designed to be flexible and easily adaptable to different email management needs while maintaining security and privacy standards.
by Kumar Shivam
AI Lead Intelligence & Outreach: Verified Emails, HubSpot Sync & Outlook Drafts Who is this for? This workflow is designed for sales/RevOps teams, B2B founders, SDR/AE teams, and agencies who live in HubSpot and need consistent, compliant first-touch outreach at scale. If you regularly build reusable, multi-client n8n automations, this template will save you hours of manual work. What problem is this workflow solving? / Use case Manual lead handling is slow and inconsistent: Leads arrive messy across forms, lists, and imports; ownership and priority are unclear. Finding the right decision-maker and a deliverable email takes too long. Outreach copy drifts from brand guidelines, and CRM updates get missed. This workflow solves the problem by creating a reliable pipeline from capture → enrichment → verification → CRM sync → Outlook draft, cutting handoffs and preserving auditability. What this workflow does Capture and batching - Triggers on new/updated leads in HubSpot or pulls "ready" rows from Google Sheets; processes items sequentially to stay rate-safe. Normalize and score (ICP) - Cleans names, company, and domains; applies configurable ICP rules and writes score plus reasoning back to HubSpot/Sheets. Enrich contacts - Confirms official company details and identifies likely decision-makers via focused people searches; dedupes and role-normalizes. Verify emails - Finds work emails, checks deliverability, and logs confidence and timestamps to a tracking sheet immediately after each result. Compose outreach - Calls the approved template in Email content; personalizes only the first name; validates structure via Structured Output Parser. Draft in Outlook - Uses Microsoft Graph to create an HTML draft; embeds an inline signature image fetched from Google Drive. CRM sync and tasks - Creates/updates HubSpot contacts and associations, stores the composed email in properties, and opens a next-day follow-up task for the owner. Safety and observability - Deterministic prompts, strict parsing, idempotent writes, and clear flags prevent duplicates; optional Slack/Teams alerts for failures. Setup Connect your accounts: HubSpot (app token) Microsoft Graph (OAuth2) Google Sheets Google Drive Your LLM provider (for Level 2 Orchestrator and Email content) Set your credentials in the respective nodes. Adjust the Google Sheet IDs to match your own sheet structure. Map HubSpot properties (owner, contact/company IDs, custom fields for score, reasoning, and email content). Paste your approved HTML in Email content and upload your signature image to Drive. Configure schedule, batch size, and any Slack/Teams webhooks for notifications. How to customize this workflow to your needs ICP logic**: Edit scoring weights and required qualifiers (industry, region, size, tech stack). Personas**: Change role detection and caps (e.g., Ops, Finance, Procurement). Copy control**: Swap the template in Email content or add A/B variants while keeping structure validation. Triggers**: Use webhook capture from forms, list-based pulls, or time-based recrawls. Delivery**: Switch the mail node to Gmail API if preferred; keep the same compose/verify/track sequence. Governance**: Add holdouts, opt-out checks, and rate limits per domain or owner; expand logs for export to a data warehouse. ✨ With this workflow, you go from messy inbound leads → verified contacts → synchronized HubSpot records → ready-to-send Outlook drafts in just minutes, with almost no manual work. Need help customizing? Contact me for consulting and support: click here
by iamvaar
Workflow explaination video: https://youtu.be/z1grVuNOXMk Prerequisites Before running this workflow, you need to have the following set up: JotForm: A form with fields for describing the issue and optionally naming the team member involved. Google Sheet 1 (Issue Resolver Logic): A sheet with three columns: Issue Category, Normal Resolver, and Alternate Resolver. This sheet defines who handles which type of complaint. Google Sheet 2 (Issue Logs): A sheet to store all submitted complaints. It needs columns like: Issue, The person Caused by, case_awarded_to, resolver_email, email_subject, email_body_html, submitted_time, and status. Google Sheet 3 (Resolver Details): A simple sheet with two columns: resolver (e.g., "HR Team") and email (e.g., "hr@yourcompany.com"). Credentials: You need to have connected accounts (credentials) in n8n for JotForm, Google (a Service Account for Sheets and OAuth for Gmail), and a Gemini API Key. Part 1: Initial Complaint Processing This part of the workflow triggers when a new complaint is submitted, uses AI to process it, logs it, and sends an initial notification. 1. JotForm Trigger What it is:** The starting point of the workflow. How it works:** It constantly listens for new submissions on your specified JotForm. When someone fills out and submits the form, this node activates and pulls in all the submitted data (like the issue description and the person involved). 2. AI Agent What it is:** The "brain" of the operation, which orchestrates several tools to make a decision. How it works:** This node receives the complaint details from the JotForm Trigger. It follows a detailed prompt that instructs it to perform a sequence of tasks: Classify: Analyze the complaint description to categorize it. Reason: Use its connected "tools" to figure out the correct resolver based on your business logic. Generate: Create a complete email notification and format the final output as a JSON object. Connected Tools:** Google Gemini Chat Model: This is the actual language model that provides the intelligence. The AI Agent sends its prompt and the data to this model for processing. Issue Resolver Allotment Logic Sheets tool: This allows the AI Agent to read your first Google Sheet. It can look up the issue category and find the designated "Normal Resolver" or "Alternate Resolver." Resolver Details Sheets tool: This allows the AI Agent to read your third Google Sheet. Once it knows the name of the resolver (e.g., "HR Team"), it uses this tool to find their corresponding email address. Structured Output Parser: This ensures that the AI's response is perfectly formatted into the required JSON structure (email, case_awarded_to, email_subject, etc.), making it reliable for the next steps. 3. Save Complaint (Google Sheets Node) What it is:** The record-keeping step. How it works:* This node takes the structured JSON output from the *AI Agent* and the original data from the *JotForm Trigger**. It then adds a new row to your second Google Sheet ("Issue Logs"), mapping each piece of data to its correct column (Issue, case_awarded_to, submitted_time, etc.). 4. Send a message (Gmail Node) What it is:** The initial notification step. How it works:* After the complaint is successfully logged, this node sends an email. It uses the resolver_email, email_subject, and email_body_html fields generated by the *AI Agent** to send a formal assignment email to the correct department or person. Part 2: Daily Follow-Up This second, independent part of the workflow runs every day to check for unresolved issues that are older than three days and sends a reminder. 1. Schedule Trigger What it is:** The starting point for the daily check-up. How it works:** Instead of waiting for a user action, this node activates automatically at a predefined time each day (e.g., 10:00 AM). 2. Get Complaint Logs (Google Sheets Node) What it is:** The data gathering step for the follow-up process. How it works:* When the schedule triggers, this node reads *all** the rows from your "Issue Logs" Google Sheet, bringing every recorded complaint into the workflow for evaluation. 3. If Node What it is:** The decision-making step. How it works:* This node examines each complaint passed to it from the previous step one by one. For each complaint, it performs a calculation: it finds the difference in days between the submitted_time and the current date. If that difference is *greater than or equal to 3**, the complaint is passed on to the next step. Otherwise, the workflow stops for that complaint. 4. Send a message1 (Gmail Node) What it is:** The reminder email step. How it works:* This node only receives complaints that met the "3 days or older" condition from the *If** node. For each of these old complaints, it sends a follow-up email to the resolver_email. The email body is dynamic, mentioning how many days have passed and including the original issue description to remind the resolver of the pending task.
by Techno
Who’s it for This workflow is ideal for sysadmins, DevOps engineers, and IT teams who want to monitor server health automatically and receive instant email notifications if any server goes down. It’s perfect for anyone managing multiple servers or services without setting up a full-fledged monitoring tool. How it works / What it does The workflow periodically sends HTTP requests to your server endpoints to check availability and response times. If a server responds with an error code or times out, the workflow automatically sends an email alert with the server details, including the endpoint, status, and timestamp. Multiple servers can be monitored in parallel, ensuring that issues are detected and reported in real time. How to set up Import the workflow template into n8n. Replace the credentials with your credentials. Configure the Email node with your SMTP credentials stored securely in n8n Credentials. Set the Cron node interval to the frequency you want the checks to run (e.g., every 5 minutes). Requirements n8n instance (self-hosted or cloud) SMTP email credentials (Gmail, Outlook, or any SMTP server) Servers with endpoints accessible by n8n
by Davide
This workflow automates the process of transcribing audio/video files into text using ElevenLabs Speech-to-Text, saving the transcripts to Google Docs, and generating AI-powered summaries and analysis, which are then emailed to a specified address. This ElevenLabs Speech-to-Text model excels in scenarios requiring accurate speech-to-text conversion: Transcription Services: Perfect for converting audio/video content to text Meeting Documentation: Ideal for capturing and documenting conversations Content Analysis: Well-suited for audio content processing and analysis Multilingual Recognition: Supports accurate transcription across 99 languages Files up to 3 GB in size and up to 10 hours in duration are supported. This API supports uploading both audio and video files for transcription. Key Advantages ✅ Automation of Repetitive Tasks: Eliminates manual transcription, note-taking, and reporting. ✅ High-Accuracy Transcription: Powered by ElevenLabs, supporting multiple languages and long files. ✅ Structured Insights: AI-powered analysis (Gemini) transforms raw transcripts into professional summaries with action items and key decisions. ✅ Seamless Integration: Works with Google Sheets, Google Docs, and Gmail for easy workflow adoption. ✅ Scalable & Reusable: Handles multiple recordings in batch and integrates smoothly into existing processes. ✅ Improved Productivity: Teams save time by receiving clear, well-structured meeting recaps without effort. How It Works The workflow operates in a linear sequence, processing one audio URL at a time from a Google Sheet. Trigger & Data Fetch: The process starts manually. It first reads from a specified Google Sheet to get a list of audio file URLs that haven't been processed yet (marked with "DONE"). Transcription: For each audio URL, it sends a request to the ElevenLabs Speech-to-Text API, passing the cloud storage URL of the audio file. Document Creation & Storage: Upon receiving the transcription text from ElevenLabs, the workflow: Creates a new Google Doc named after the transcription ID. Writes the full raw transcript text into this newly created document. Analysis & Summary: The raw transcript text is passed to Google Gemini AI. The AI analyzes the text based on a detailed, pre-defined system prompt that instructs it to extract key points, decisions, action items, and insights, formatting the output as a structured summary. Notification: The AI-generated analysis (converted from Markdown to HTML) is sent via Gmail as an email to a predefined address. Status Update: Finally, the workflow updates the original row in the Google Sheet, marking it as "DONE" (with an 'x') and recording the ID of the newly created Google Doc for future reference. This ensures the same audio file is not processed again on the next run. Set Up Steps To configure this workflow, you need to complete the following steps: Credentials Setup: ElevenLabs API: In the "Speech-to-Text" HTTP Request node, configure the HTTP Header Auth credentials. The header name should be xi-api-key and the value should be your valid ElevenLabs API key. Google Services: Ensure your Google Sheets, Google Docs, and Gmail nodes are connected to valid Google OAuth2 credentials with the necessary permissions to read, write, and send emails. Google Gemini AI: The "Transcript Analysis" node must be connected to valid Google Gemini (PaLM) API credentials. Google Sheet Configuration: Make a copy of the provided Google Sheet template. In the "Get audio urls" node, update the documentId parameter to match the ID of your new Google Sheet. Similarly, update the documentId in the "Update row" node. Populate your sheet with the URLs of the audio/video files you want to process in the 'AUDIO URL' column. Output Configuration: In the "Send email" node, change the sendTo parameter to the email address where you want to receive the analysis summaries. The "Create Doc" node specifies a folderId; change this to the ID of the specific Google Drive folder where you want the transcripts to be saved. Need help customizing? Contact me for consulting and support or add me on Linkedin.
by Yassin Zehar
Description Automated workflow that generates a Sprint Report from Jira and delivers it by Gmail. The flow fetches sprint issues from Jira, validates and normalizes the data, calculates metrics (tickets, story points, blockers, completion rate), generates an HTML report, and sends it by email. Context This template helps teams keep stakeholders updated automatically of the current sprint. Instead of manually compiling Jira data, the report is generated and sent on schedule (e.g., every Friday at 17:00). It’s production-friendly, reusable, and works across Jira projects. Target Users Scrum Masters and Agile Coaches who need sprint reports for retrospectives. Product Owners who want a weekly overview of sprint progress. Project Managers tracking Jira delivery KPIs. Engineering teams wanting automated status reporting without extra overhead. Technical Requirements Jira Cloud project + API email + API token + permission to read issues. Gmail credential for notifications. Workflow Steps Trigger – Schedule (e.g., Friday at 17:00). Edit Fields – Configure Jira base URL, project key, email recipients. Get Many Issues – Fetch sprint issues with JQL (project = <KEY> AND sprint in openSprints()). Validation & Normalization – Clean/validate fields (status, assignee, priority, story points, sprint info). Metrics Calculation – Aggregate KPIs (done, in progress, blockers, story points, completion %). HTML Report Generation – Build a styled email-friendly HTML summary + detailed table. Send Gmail – Deliver report to stakeholders. Key Features Automated Sprint Reports: No manual copy-paste. Metrics overview: Tickets done vs total, blockers, story points. Detailed table: Issue key, summary, status, assignee, priority, SP. Email delivery: HTML report with Jira links sent to stakeholders. Fully customizable: Adjust fields, KPIs, and recipients easily. Expected Output 📊 HTML Sprint Report with KPIs and issue table. ✅ Email delivered to stakeholders via Gmail. 🔗 Jira links embedded for easy navigation. How it works ⏰ Trigger – Runs on schedule (e.g., every Friday at 17:00). 🧾 Fetch Issues – JQL filters sprint tickets. 📊 Metrics – Done vs total, SP progress, blockers. 💻 Generate HTML – Clean, styled table and summary. ✉️ Notify – Send Gmail with full sprint report to stakeholders. Tutorial video: Watch the Youtube Tutorial video About me : I'm Yassin, IT Project Manager, Agile & Data specialist. Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin
by Khaisa Studio
Secure your perfect Malaysian identity with the Khaisa Domain Sniper. This n8n workflow monitors specific .my domains using the free MYNIC RDAP API, instantly triggering Gmail and Discord alerts the moment a domain becomes available for registration, ensuring you never miss a high-value branding opportunity again. Why Use This Workflow? Time Savings: Eliminates the need for manual WHOIS lookups, saving roughly 2 hours of repetitive checking per week. Error Prevention: Automated 24/7 monitoring ensures you are notified within 30 minutes of a domain status change, preventing competitors from "sniping" your target. Scalability: Effortlessly monitor a list of 10, 50, or 100+ domains by simply adding rows to a Google Sheet. Ideal For Digital Agencies:** Monitor expiring client brand names or high-value industry keywords for SEO benefits. Startup Founders:** Secure the perfect .my or .com.my domain for a new venture as soon as it is released. Domain Investors:** Automate the "sniping" process for expired Malaysian domains to build a valuable portfolio. How It Works Trigger: A scheduled trigger initiates the process every 30 minutes. Data Collection: The workflow pulls a list of target domains from a Google Sheet where the status is marked as "no" (not available). Processing: A loop iterates through each domain, preparing individual requests. Intelligence Layer: The workflow queries the official MYNIC RDAP public API to check the real-time registration status. Output & Delivery: If the API confirms availability, the system sends a professionally styled HTML email via Gmail and a notification to a Discord channel. Storage & Logging: The Google Sheet is automatically updated to "yes" for available domains to prevent duplicate alerts. Setup Guide Prerequisites | Requirement | Type | Purpose | |-------------|------|---------| | n8n instance | Essential | Workflow execution platform | | Google Sheets | Essential | Central database for target domains | | Gmail Account | Essential | To send stylized HTML availability alerts | | Discord Bot | Optional | For instant push notifications to your team | | MYNIC RDAP | Public | No API key required for .my domain lookups | Installation Steps Import the JSON file to your n8n instance Configure credentials: Google Sheets: Connect your Google account and select your "Domain Target" spreadsheet. Gmail: Authenticate the Gmail node to allow the system to send alerts from your address. Discord: Add your Bot Token and Channel ID if you wish to receive Discord alerts. Prepare your Google Sheet: Create two columns: Domain and isAvailable. Add your target domains (e.g., brandname.my) and set isAvailable to no. Customize settings: Adjust the Schedule Trigger to your preferred frequency (e.g., every 15 or 30 minutes). Test execution: Run the workflow manually with one "available" test domain to confirm the email and Discord formatting. Technical Details Core Nodes | Node | Purpose | Key Configuration | |------|---------|-------------------| | RDAP: Check Status | Fetch API Data | Uses https://rdap.mynic.my/rdap/domain/{domain} | | Domain Available? | Logic Gate | Checks if response contains "is available for registration" | | Gmail Alert | Notification | Sends custom HTML template with "Register Now" button | | Update Sheet | Data Sync | Switches isAvailable to yes upon discovery | Workflow Logic The workflow uses a "Split in Batches" approach combined with a 10-second Wait Node. This is critical for performance as it prevents hitting MYNIC rate limits when checking long lists of domains, ensuring high reliability and preventing your IP from being temporarily blocked. Customization Options Basic Adjustments: Check Frequency:** Change the cron schedule from 30 minutes to 5 minutes for high-priority domains. Wait Duration:** Increase the 10-second wait if you are monitoring more than 100 domains in a single run. Advanced Enhancements: Auto-Registration:** Connect a registrar API (like OpenSRS or Hexonet) to automatically attempt registration. Multi-Extension:** Expand the logic to check .com, .net, or .io domains by adding conditional URL logic for different RDAP providers. Performance & Optimization | Metric | Expected Performance | Optimization Tips | |--------|---------------------|-------------------| | Execution time | ~12s per domain | Parallel processing can be enabled for small lists | | API calls | 1 per domain | Only processes domains marked as isAvailable = no | | Error handling | "Never Error" active | HTTP node is set to continue even if the API times out | Troubleshooting Common Issues: | Problem | Cause | Solution | |---------|-------|----------| | 429 Too Many Requests | Checking too fast | Increase the time in the Wait 10 Seconds node | | Gmail Authentication Error | Token expired | Re-connect your Google OAuth2 credentials | | Sheet not updating | Column name mismatch | Ensure headers in GSheets match the node mapping exactly | Use Case Examples Scenario 1: Brand Protection Challenge: A competitor currently owns a .my domain that matches your .com brand, and you are waiting for it to expire. Solution: This workflow monitors the domain 24/7 and alerts your legal team the moment it hits the "Available" status. Result: You secure your local brand identity without paying a premium to a domain broker. Scenario 2: Professional Domain Flipping Challenge: You have a list of 50 high-value keywords you want to acquire as they drop from the registry. Solution: Add the list to Google Sheets. The workflow checks them every 30 minutes and notifies your Discord "Sniper" channel. Result: You are always the first to know, allowing you to register prime digital real estate before others. Created by: Khaisa Studio Category: Productivity | Tags: Domain, Automation, Monitoring, MYNIC, RDAP Need custom workflows? Contact us Connect with the creator: Portfolio • Workflows • LinkedIn • Medium • Threads
by Sandeep Patharkar | ai-solutions.agency
Outlook Inbox Tamer: AI-Powered Categorization, Auto Replies & Team Alerts This workflow automatically classifies and routes incoming Outlook emails into smart categories using n8n + OpenAI GPT-4.1-mini. It helps professionals and teams stay organized by intelligently sorting and responding to high-priority messages, customer support emails, promotions, and finance-related messages — all without manual effort. 🧠 Who’s It For Professionals or teams overwhelmed by email volume. Customer support, operations, or finance teams needing real-time triage. Anyone who wants AI to help manage and prioritize their Outlook inbox. ⚙️ How It Works Microsoft Outlook Trigger monitors your inbox for new emails. OpenAI GPT-4.1-mini analyzes each email and classifies it as one of: High_Priority Customer_Support Promotions Finance/Billing Routing node moves emails to matching Outlook folders. AI-generated replies and Telegram notifications keep the right team informed instantly. (Optional) Use Google Sheets + Manual Trigger to test with sample data before going live. 🛠️ Requirements Outlook account connected via Microsoft Outlook OAuth2. OpenAI API key** (set up in n8n credentials). (Optional) Telegram bot token for team alerts. (Optional) Google Sheets for test emails. 🔧 How to Set Up Import the workflow into your n8n instance. Add credentials for: Microsoft Outlook OpenAI Telegram (optional) Deploy and activate the workflow. Start sending or receiving emails — watch them get auto-classified and organized! 🧩 How to Customize Update the system prompt in the Email_Classifier_Agent to add more categories (like HR, Legal, etc.). Change Telegram recipients for alerts. Extend the workflow to post classified data into Notion, Slack, or CRM. 📘 Example Use Case An AI agent monitors your Outlook inbox, classifies incoming emails in real time, moves them to their respective folders, creates response drafts, and alerts your team instantly through Telegram. 💬 Connect with the Creator 👋 Created by Sandeep Patharkar 💼 Connect on LinkedIn 🌐 Join my Skool community for n8n + AI automation tutorials, live Q&As, and exclusive workflow templates. Category: Email Automation / AI Productivity Difficulty: Intermediate Estimated Setup Time: ⏱️ 10–15 minutes
by Yassin Zehar
Description This workflow sends an instant email alert when a task in a Google Sheet is marked as Urgent, and then sends a Telegram reminder notification after 2 hours if the task still hasn’t been updated. Then a Jira ticket is created so the task enters in the formal workflow and another Telegram message is sent with the details of the issue created. It helps teams avoid missed deadlines and ensures urgent tasks get attention — without requiring anyone to refresh or monitor the sheet manually. Context In shared task lists, urgent items can be overlooked if team members aren't actively checking the spreadsheet. This workflow solves that by: Sending an email as soon as a task becomes Urgent Waiting 2 hours Checking if the task is still open Sending a Telegram reminder only if action has not been taken Creating a Jira issue Sending a Telegram message with the details of the issue created This prevents both silence and spam, creating a smart and reliable alert system. Target Users Project Managers using Google Sheets Team leads managing shared task boards Remote teams needing lightweight coordination Anyone who wants escalation notifications without complex systems Technical Requirements Google Sheets credential Gmail credential Telegram Bot + Chat ID Google Sheet with a column named Priority Jira credential Workflow Steps Trigger: Google Sheets Trigger (on update in the “Priority” column) IF Node – Checks if Priority = Urgent Send Email – Sends alert email with task name, owner, status, deadline Mark Notified = Yes in the sheet Wait 2 hours IF Status is still not resolved Send Telegram reminder create an Issue on Jira based on the information provided Send Telegram message with the details of the ticket Key Features Real-time alerts on critical tasks Simple logic (no code required) Custom email body with dynamic fields Works on any Google Sheet with a “Priority” column Telegram notification ensures the task doesn’t get forgotten Expected Output Personalized email alert when a task is marked as "Urgent" Email includes task info: title, owner, deadline, status, next step Telegram message after 2 hours if the task is still open Automatic creation of a Jira issue with the higgest priority Telegram message to notify about the new Jira ticket How it works Trigger: Watches for “Priority” updates 🔍 Check: If Priority = Urgent AND Notified is empty 📧 Email: Sends a personalized alert ✏️ Sheet Update: Marks the task as already notified ⏳ Wait: 2-hour delay 🤖 Check Again: If Status hasn’t changed → send Telegram reminder, create Jira ticket and send the details. Tutorial video: Watch the Youtube Tutorial video About me : I'm Yassin, IT Project Manager, Agile & Data specialist. Scaling tech products with data-driven project management. 📬 Feel free to connect with me on Linkedin
by Naveen Choudhary
Who's it for This workflow is designed for venture capitalists, private equity professionals, investment analysts, and financial researchers who need to track private securities offerings and fundraising activities in real-time. It's particularly valuable for firms building deal flow pipelines, monitoring competitor fundraising, or conducting private market research. What it does This automation continuously monitors the SEC's EDGAR database for new Form D filings, which companies file when raising capital through private placements. Every 10 minutes during business hours (Monday-Friday, 6 AM - 9 PM), it checks for new filings, downloads the complete documents, and extracts critical information into a structured Google Sheets database. The workflow captures comprehensive details including company name and contact information, key executives and their roles, fund classification, target offering amount, current capital raised, total investor count, sale status, filing dates, and regulatory exemptions being utilized (such as Rule 506(b) or 3(c)(7)). How it works The workflow operates in five main stages: Stage 1 - Feed Monitoring: A scheduled trigger activates every 10 minutes during business hours, fetching the latest Form D filing feed from the SEC EDGAR system in XML format. Stage 2 - Initial Processing: The XML feed is parsed to extract basic filing metadata including CIK numbers, company names, form types, and document URLs. The system then filters out any previously processed filings using deduplication logic and adds only new filings to your Google Sheet tracking database. Stage 3 - Selective Processing: The workflow identifies unprocessed Form D and Form D/A (amendment) filings that need detailed extraction, filtering out other form types and already-processed entries. Stage 4 - Deep Data Extraction: For each unprocessed filing, the workflow downloads the complete Form D text document, parses the embedded XML structure, and systematically extracts four categories of information: issuer details (company name, address, CIK, jurisdiction, entity type, industry classification), key personnel (executives, directors, promoters with their specific roles), offering information (total offering amount, amount already sold, remaining amount, investor count, accredited investor status), and regulatory details (exemptions claimed, sale status, offering duration). Stage 5 - Database Update: All extracted data is consolidated into a summary format and used to update the corresponding row in your Google Sheet, marking the filing as "processed". A wait node introduces a brief delay between document retrievals to comply with SEC rate limiting policies. Requirements To use this workflow, you'll need: A Google Sheet configured with these specific columns: cikNumber, title, formType, filingLinkHtml, filingLinkTxt, updated, companyName, keyExecutive, executiveRole, fundType, targetAmount, amountRaised, investorCount, salesStatus, filingDate, exemptions, status, and comment Google Sheets OAuth2 credentials connected in n8n to enable read/write access Compliance with SEC EDGAR requirements: you must update the User-Agent headers in both HTTP Request nodes (replacing the placeholder email with your own valid email address as required by SEC's fair access policy) Setup instructions Step 1: Create or prepare your Google Sheet with the exact column structure listed in the requirements section. Note your Google Sheet ID from the browser URL. Step 2: In n8n, configure your Google Sheets OAuth2 credentials through the credentials panel. Test the connection to ensure it's working properly. Step 3: Open both Google Sheets nodes in the workflow ("Add New Filing to Tracking Sheet" and "Update Filing Status in Sheet"). Update the Document ID field with your Google Sheet ID. Step 4: Critical compliance step - Open both HTTP Request nodes ("Fetch SEC Form D Feed" and "Retrieve Form D Document"). In the headers section, replace nchoudhary110792@gmail.com with your actual email address. The SEC requires this for their access logs. Step 5: Test the workflow manually first by clicking "Execute Workflow" to ensure everything connects properly and data flows to your sheet correctly. Step 6: Once verified, activate the workflow using the toggle switch. It will now run automatically on the configured schedule. Customization options Adjust monitoring frequency: Modify the Schedule Trigger node's cron expression to run more or less frequently. The default */10 6-21 * * 1-5 runs every 10 minutes during business hours on weekdays. Filter by fund type or size: Add a Filter (IF) node after "Consolidate Filing Data" to only process filings that meet specific criteria (e.g., offerings above $10M, specific fund types like hedge funds or venture capital). Add real-time notifications: Connect a Slack, Discord, or Email node after "Update Filing Status in Sheet" to receive instant alerts when high-priority filings are detected (based on criteria you define). Enrich with external data: Add HTTP Request nodes to query APIs like Crunchbase, PitchBook, or LinkedIn to supplement SEC data with additional company intelligence, funding history, or executive backgrounds. CRM integration: Replace or supplement the Google Sheets nodes with connections to your CRM (Salesforce, HubSpot, Pipedrive) to automatically create deal records or update company profiles when relevant filings appear. Historical analysis: Add a Set node to calculate metrics like month-over-month filing volume, average raise sizes by industry, or track specific companies' filing patterns over time. Multi-sheet organization: Use Router nodes to send different filing types to separate sheets (e.g., venture capital funds vs. hedge funds vs. real estate offerings) for easier analysis.