Workflow Templates

Unleash the full potential of your website's search engine performance and user experience with this all-in-one n8n automation template. Designed for SEO professionals and webmasters, this suite provides meticulous on-page and technical SEO auditing, deep insights into Core Web Vitals (LCP & INP), and an intelligent AI-powered chatbot for instant insights and troubleshooting. Key Features: Comprehensive On-Page SEO Audit: Automatically checks for **missing or malformed titles, meta descriptions, H1s (including multiple H1s), missing alt text on images, and canonical tag issues. Detailed Technical SEO Scan: Verifies **HTTPS implementation, robots.txt accessibility and content, and sitemap.xml presence. Core Web Vitals Monitoring: Leverages **Google PageSpeed Insights to continuously track and alert on critical performance metrics like Largest Contentful Paint (LCP) and Interaction to Next Paint (INP). AI-Powered Analysis & Recommendations: Integrates advanced AI models (ChatGPT, Claude, or Gemini) to **analyze audit findings, provide actionable recommendations for improvements, and even suggest better alt text for images based on content context. Intelligent SEO Chatbot: A dynamic chatbot triggered by webhooks understands natural language queries, extracts entities (URLs, keywords, SEO topics), and provides **instant, AI-generated answers about SEO best practices, Core Web Vitals explanations, or even specific site data (via Google Search Console integration). Automated Reporting & Alerts: Logs all audit data to **Google Sheets for historical tracking and sends real-time Slack alerts for critical SEO issues or performance degradations. Streamline your SEO workflow, ensure optimal website health, and react swiftly to performance challenges. This template is your ultimate tool for staying ahead in the competitive digital landscape.

📘 Description This automation streamlines developer billing and compliance tracking by integrating Jira, Gmail, and n8n into a single intelligent workflow. It fetches all project issues from Jira, calculates logged hours per team member, identifies missing time entries, and automatically generates professional invoice summaries — complete with text attachments — which are then emailed to each developer. The system ensures no time logs are missed, billing remains accurate, and finance teams receive transparent, auditable records — all without manual follow-ups. ⚙️ What This Workflow Does (Step-by-Step) 🟢 When Clicking ‘Execute Workflow’ Starts the entire billing and compliance cycle manually or on schedule. 📋 Fetch All Project Issues with Time Data Retrieves all Jira issues across projects, including: Time spent (seconds → hours) Assignee, project, sprint, and status info Priority and issue summaries This serves as the foundation for billing calculations and compliance checks. 📊 Aggregate Hours by Team Member Groups issues by assignee and calculates total hours logged per person. Outputs per-user data with: Name & email Total logged hours Full issue breakdown (status, sprint, priority) Forms the core dataset for both invoice creation and reminder logic. ⚠️ Identify Issues with Missing Time Logs Scans aggregated data to find issues where time = 0 hours. Generates HTML reminders with: Table of unlogged issues (key, summary, sprint, status) Personalized note urging time entry completion Only sends reminders to users who actually missed logs. Prevents manual follow-up and ensures billing accuracy. 💰 Generate Invoice Summary with Text Attachment Creates text-based invoice documents for each user with logged hours. Includes: Itemized issue breakdowns Hourly rate (default: $50/hr) Total hours & billing amount Auto-generated timestamp Exports invoices as text attachments (Invoice_{Assignee}.txt) in base64. 🔗 Combine Reminder & Invoice Data Streams Merges invoice data and reminder data into one unified stream, ensuring: All users (with or without logged hours) are processed Emails contain correct context and attachments Enables complete communication coverage in a single workflow. 🔧 Reconcile JSON & Binary Attachments Smartly merges JSON email metadata and binary invoice files post-merge. Handles complex data cases (missing binary or JSON) using fallback logic. Guarantees each email has a valid recipient and invoice attachment. 📧 Send Invoices & Reminders to Team Sends personalized emails to each developer with: Subject: project name Body: hours summary & reminder message Attachment: invoice text file (if available) Emails are automatically delivered via Gmail with audit trails. 🧩 Prerequisites Jira Software Cloud API credentials Gmail OAuth2 connection Configured hourly billing rate (default: $50/hr) Active n8n instance (self-hosted or cloud) 💡 Key Benefits ✅ Eliminates manual invoice generation ✅ Ensures accurate time tracking & compliance ✅ Sends automated reminders for missing hours ✅ Provides transparent, auditable billing communication ✅ Saves finance & project teams hours of manual effort 👥 Perfect For Tech & IT service companies billing by developer hours Project managers tracking time compliance Finance teams ensuring timely invoicing Agencies managing multiple sprint-based projects

Who is this for? This workflow is ideal for WooCommerce store owners who want to automatically send promotional WhatsApp messages to their customers when new coupons are created. It’s designed for marketers and eCommerce managers looking to boost engagement, streamline coupon sharing, and track campaign performance effortlessly through Google Sheets. Overview This workflow listens for WooCommerce coupon creation events (coupon.created) and uses customer billing data to send promotional WhatsApp messages via the Rapiwa API. The flow formats the coupon data, cleans phone numbers, verifies WhatsApp registration with Rapiwa, sends the promotional message when verified, and logs each attempt to Google Sheets (separate sheets for verified/sent and unverified/not sent). What this Workflow Does Listens for new coupon creation events in WooCommerce via the WooCommerce Trigger node Retrieves all customer data from the WooCommerce store Processes customers in batches to control throughput Cleans and formats customer phone numbers for WhatsApp Verifies if phone numbers are valid WhatsApp accounts using Rapiwa API Sends personalized WhatsApp messages with coupon details to verified numbers Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Automated coupon distribution: Triggers when new coupons are created in WooCommerce Customer data retrieval: Fetches all customer information from WooCommerce Phone number validation: Verifies WhatsApp numbers before sending messages Personalized messaging: Includes customer name and coupon details in messages Dual logging system: Tracks both successful and failed message attempts Rate limiting: Uses batching and wait nodes to prevent API overload Data formatting: Structures coupon information for consistent messaging Google Sheet Column Structure A Google Sheet formatted like this ➤ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: | name | number | email | address1 | couponCode | couponTitle | couponType | couponAmount | createDate | expireDate | validity | status | | ----------- | ------------- | --------------------------------------------------- | --------- | ---------- | -------------- | ---------- | ------------ | ------------------- | ------------------- | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | verified | sent | Requirements n8n instance with the following nodes: WooCommerce Trigger, Code, SplitInBatches, HTTP Request, IF, Google Sheets, Wait WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) Important Notes Phone Number Format**: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits**: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy**: Ensure compliance with data protection regulations when sending marketing messages. Error Handling**: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Message Content**: The current message template references the first coupon only (coupons[0]). Adjust if you need to handle multiple coupons. Useful Links Dashboard:** https://app.rapiwa.com Official Website:** https://rapiwa.com Documentation:** https://docs.rapiwa.com Support & Help WhatsApp**: Chat on WhatsApp Discord**: SpaGreen Community Facebook Group**: SpaGreen Support Website**: https://spagreen.net Developer Portfolio**: Codecanyon SpaGreen

Automatically turn incoming support emails into categorized, prioritized tasks in Dart—complete with AI-generated summaries, tags, and sender context. What It Does This workflow captures emails from Gmail, uses an AI model to classify them into one of seven categories (e.g., Bug Report, Billing, Feature Request), and creates a structured task in Dart. Each task includes: Title**: The email subject Tag**: Based on the detected category Priority**: Set by the AI based on content analysis Description**: Includes confidence level, rationale, summary, and the cleaned full email body Comment**: Automatically adds the sender’s name and email for easy reference The workflow also parses and cleans the raw HTML email content, ensuring all data is readable and workflow-ready. Who's It For This template is built for support and operations teams using Dart who want to streamline how incoming emails are sorted and turned into actionable tasks. It’s ideal for organizations managing multiple types of requests and updates from clients, partners, or systems. How to Set Up Import the workflow into n8n Connect your Gmail and Dart accounts Replace the dummy Dartboard ID with your actual board ID Choose your preferred AI model (results may vary depending on model quality) If your target email address is in a google group, use the Filter: "Sender" in the Gmail trigger Requirements n8n account Connected Gmail and Dart account How to Customize the Workflow Modify the category list to match your team’s taxonomy Adjust the AI classification prompt to fine-tune tagging and prioritization Choose your preferred AI model

This workflow automates the entire lifecycle of collecting, filtering, summarizing, and delivering the most important daily news in technology, artificial intelligence, cybersecurity, and the digital industry. It functions as a fully autonomous editorial engine, combining dozens of RSS feeds, structured data processing, and an LLM (Google Gemini) to transform a large volume of raw articles into a concise, high–value daily briefing delivered straight to your inbox. Read: Full setup Guide ✅ 1. Scheduled Automation The workflow begins with a Schedule Trigger, which runs at predefined intervals. Every execution generates a fresh briefing that reflects the most relevant news from the past 24 hours. ✅ 2. Massive Multi-Source RSS Collection The workflow gathers content from over 25 curated RSS feeds covering: 🔐 Cybersecurity (The Hacker News, Krebs on Security, SANS, CVE feeds, Google Cloud Threat Intelligence, Cisco Talos, etc.) 🤖 Artificial Intelligence (Google Research, MIT News, AI News, OpenAI News) 💻 Technology & Digital Industry (Il Sole 24 Ore, Cybersecurity360, Graham Cluley, and more) ⚙️ Nvidia Ecosystem (Nvidia Newsroom, Nvidia Developer Blog, Nvidia Blog) Each RSS feed is handled by a dedicated node, which ensures: source isolation easier debugging no single point of failure The feeds are grouped using category-specific Merge nodes (Cyber1/2/3, AI, Nvidia), enabling modular scalability. ✅ 3. Unified Feed Aggregation All category merges feed into the Merge_All node, creating a single combined dataset of articles from every source. ✅ 4. Intelligent Filtering (last 24 hours only) The Filter node removes: articles older than 24 hours (based on isoDate) invalid items duplicated or redundant entries This keeps the briefing strictly relevant to the current day. ✅ 5. Chronological Sorting The Sort – Articles by Date node orders all remaining items in descending date order. More recent or time-sensitive news is therefore prioritized. ✅ 6. Data Normalization (JavaScript Code) A dedicated Code node transforms all incoming items into one clean JSON object: { "articles": [ { "title": "...", "content": "...", "link": "...", "isoDate": "..." } ] } This standardized structure becomes the input for the LLM summarization stage. ✅ 7. AI Editorial Processing – Google Gemini The node LLM – News Summarizer is the workflow’s editorial brain. A complex prompt instructs Gemini to behave like the editor-in-chief of a major tech newspaper, enforcing strict rules: Selection rules: choose only 8–10 truly important stories ignore low-value content (minor product releases, clickbait, rumors…) Relevance criteria: AI research & foundation models Big Tech developments cybersecurity incidents regulation and digital policy semiconductors, cloud, and infrastructure digital rights, governance, sovereignty Deduplication: If multiple feeds report the same story, only one version is kept. Output format: Gemini must output a valid JSON object containing: subject: the email subject line html: a fully structured HTML body grouped into categories Each news item ends with a clickable HTML source link, NEVER plaintext URLs. This step condenses dozens of articles into a polished, editorial-grade briefing. ✅ 8. HTML Newsletter Assembly (Code Node) The Build Final Newsletter HTML node: safely parses the JSON from the LLM cleans any validates subject and html fields embeds the content into a modern, responsive HTML email template The output is a single item containing: the final email subject the final HTML body Ready to be sent. ✅ 9. Automatic Email Delivery The Send Final Digest Email (Gmail node): uses the generated subject sends the curated HTML newsletter delivers it to the configured recipient(s) uses a custom sender name (“n8n News”) The result is a fully automated Tech & AI Daily Briefing delivered with zero manual effort. In Summary: What This Workflow Achieves ✔ Collects news from 25+ high-quality RSS sources ✔ Normalizes, filters, and sorts all items automatically ✔ Uses Google Gemini to select only the stories that truly matter ✔ Generates a coherent, readable, professional-looking HTML newsletter ✔ Sends the result via email every day Perfect for: daily executive briefings technology and cybersecurity monitoring automated newsletter production internal knowledge distribution competitive intelligence workflows

AI-Powered Gmail Auto-Labeler Automatically organize your Gmail inbox with seamless, dynamic AI classification! This workflow leverages Google Gemini’s latest model to continually sort new emails into your own custom Gmail labels—no manual intervention or tedious setup required. 🚀 What This Workflow Does Watches for Unread Emails:** Continuously polls your Gmail inbox for new unread emails (polling interval can be changed as needed). Fetches All Available Labels:** Dynamically syncs every custom & system label from your Gmail account—no hardcoded lists. AI-Based Classification:** Each new email’s subject and snippet/body are sent to the Gemini 2.5 Pro AI, which analyzes content and recommends the best matching label(s) from your own label list (not made up!). Accurate Label Application:** The workflow maps Gemini’s label name suggestions to the correct label IDs in Gmail and auto-applies one or more labels directly to each email. Self-Updating / No Maintenance:** If you add/change Gmail labels, the workflow always uses the current label list. You don’t need to update any configuration or nodes (completely dynamic). Supports Multiple Simultaneous Labels:** Gemini can assign several labels at once—perfect for nuanced sorting (ex: “Receipts”, “Work”, "Travel"). 🔧 How to Set Up Connect Credentials: Google Gmail account (OAuth2) Gemini API key (for Google Gemini) (Optional) Adjust Gmail Labels: Add, rename, or customize labels in Gmail to suit your sorting preferences. You can continue to modify these at any time! Activate the Workflow: Turn on the workflow. It starts processing new emails immediately. No need to edit code or update nodes when labels change. (Optional) Customize Filtering or Post-Processing: The default trigger checks for unread messages, but you can adjust this (e.g., all messages, specific senders, etc.). Add extra workflow steps as desired for downstream automation. 📝 Key Features & Best Practices Dynamic Label Handling:** Workflow always references your live Gmail label list—ensuring AI only selects valid, current labels. Never Misses a Label:** Gemini never invents new labels; only suggests exact matches from your actual account. Highly Customizable:** Enhance/chain further automations—trigger from read emails, exclude newsletters, forward labeled messages, etc. No Manual Updates:** Completely plug-and-play. Adding/changing labels in Gmail immediately reflects in workflow. Includes In-Workflow Notes:** Clear sticky notes and documentation embedded for reference and troubleshooting. 🕰 Example Use Cases Automated Inbox Zero – Instantly sort incoming emails into actionable folders. Smart Multi-Labeling – Financial emails get “Receipts”, “Accounting” and “Work”, all at once. Personal & Work Split – Classify emails into "Personal", "Clients", "Leads", etc. Travel, Projects, Subscriptions – Transform your Gmail into a fully organized hub. This workflow is perfect for anyone who wants Gmail organization powered by leading-edge AI, with absolutely minimal maintenance. Just connect accounts and activate — let Gemini do the sorting!

Overview This n8n workflow template automates your B2B marketing follow-up process. It tracks which introductory emails have received a reply, identifies leads who haven't responded within a set time, uses Gemini AI to draft a personalized, casual reminder, sends the follow-up as a reply on the original thread, and updates your lead tracker in Google Sheets. Best if used with preivously created workflow that sends an automated introductory email with templatized subject. Requirements To use this workflow, you need the following accounts and credentials: Gmail Account: To check for replies and send the reminder emails. Google Sheets Account: To manage your lead tracking spreadsheet (the workflow uses a sheet with ID). Below are the Sheet columns *First Name Last Name Email ID Company Name Company Information (optional) Designation (optional) Message - the main form enquiry Location (optional) Status (auto) Intro email Date (auto) Reminder 1 needed? (auto) Reminder 1 Email Date (auto)* Google Gemini (PaLM) API Key: For the AI Agent node to generate the personalized email content. How It Works This automation is broken down into three main stages: Stage 1: Check for Replies and Update Tracker This stage excludes leads who have already replied to your introductory email and updates the status in your tracker. When clicking ‘Execute workflow’ (Manual Trigger): The workflow starts manually or can be scheduled. Get many messages (Gmail): The node searches your inbox (CATEGORY_PERSONAL) for replies to your introductory email (using the search query subject: <template of your introductory email>). Update row in sheet (Google Sheets): For every incoming reply found, the workflow matches the lead by Email ID and updates the column Reminder 1 needed? to No. Stage 2: Identify Who Needs a Reminder This stage finds leads who have not yet received a reminder and checks if the introductory email was sent over 5 days ago. Get row(s) in sheet (Google Sheets): The workflow retrieves all leads from the tracker where the column Reminder 1 needed? is not set to No (i.e., they haven't replied and a reminder status hasn't been logged). If: A condition checks if the Intro email Date is older than 5 days (DateTime.now().minus({ days: 5 })). Only leads that meet this age criteria are passed forward. Stage 3: Send Personalized Reminder and Final Update For eligible leads, the AI generates a follow-up, finds the original email thread, sends the reply, and logs the action. AI Agent: The AI Agent acts as a B2B marketing assistant to write a short, friendly first reminder email. It uses lead data (First Name, Company Name, Message) to personalize the content, referencing the original introductory email and the client's pain point. Note: The AI is instructed to format its output into ClientEmail and ClientEmailBody using the Structured Output Parser. Edit Fields (Set): The structured output from the AI is mapped to workflow fields. Get many messages1 (Gmail): The workflow searches the SENT label for the original email using the client's email and the introductory subject line to find the correct threadId and messageId. Reply to a message (Gmail): The personalized body is sent as a reply on the original thread to maintain context. Update row in sheet1 (Google Sheets): The final step updates the lead's row in the tracker, setting Status to Reminder 1 Drafted, Reminder 1 needed? to Yes, and recording the current date in the Reminder 1 Email Date column. Customization Currently it has option to send first reminder. This can be extended to add another reminder. Write to priyanka@buildmyaiflow.agency for more customizations.

Reply Handling (Optional Extension) This optional workflow handles email replies after availability options have been sent. It extends the main scheduling flow by enabling two-way, email-based confirmation. What this extension does Listens for user replies via Gmail Normalizes free-text replies into structured data Detects whether the user confirmed a proposed slot or requested alternatives Automatically creates a Google Calendar event on confirmation Sends a confirmation or follow-up email accordingly Why this matters Most scheduling automations stop after sending availability. This extension closes the loop by turning email replies into real actions — without requiring booking links or manual follow-ups. Typical reply examples 1 → Confirms the suggested time and creates the calendar event 2 → Requests alternative time slots and continues the scheduling flow When to use this Email-first scheduling (no Calendly / booking pages) High-touch or human-like scheduling flows Sales calls, interviews, consultations, internal meetings

Smart Lead Qualification for JotForm Contact Forms Automatically classify and manage contact form submissions using AI-powered lead scoring. This workflow analyzes JotForm submissions in real-time, categorizes them as hot leads, cold leads, or spam, and takes intelligent actions—sending Telegram notifications for hot leads, ignoring irrelevant inquiries, and automatically deleting spam. Who's It For This template is perfect for: Businesses receiving high volumes of contact form submissions** who need to prioritize responses Marketing and sales teams** wanting to focus on qualified leads immediately Agencies and consultants** offering AI/automation services who want to filter out noise Anyone struggling with spam** or low-quality form submissions What It Does The workflow uses Google Gemini AI to intelligently classify each JotForm submission into three categories: Hot Lead (1)**: Genuine inquiries about your services, collaboration requests, or project proposals → Sends Telegram notification + Flags in JotForm Cold Lead (0)**: Legitimate but irrelevant inquiries (job applications, unrelated business queries) → No action taken Garbage/Spam (2)**: Test submissions, bots, gibberish, or fake data → Automatically deleted from JotForm How It Works JotForm trigger captures new contact form submissions Submission data is extracted and formatted Google Gemini AI analyzes the content and classifies the lead A switch routes the submission based on classification: Hot leads trigger Telegram notifications and get flagged Cold leads are ignored Spam submissions are automatically deleted Requirements n8n instance** (cloud or self-hosted) JotForm account** with a contact form (Get JotForm here) Google Gemini API key** (free tier available) Telegram account** for notifications How to Set Up 📋 Detailed setup instructions are included inside the workflow in sticky notes. Quick setup overview: Create your contact form in JotForm using the "Contact Form with Fancy Header and Footer" template Get your JotForm API key and form ID Obtain a Google Gemini API key from Google AI Studio Create a Telegram bot via @BotFather and get your chat ID Configure all credentials in the respective nodes Update the HTTP request nodes with your JotForm API key Test the workflow with sample submissions The workflow includes comprehensive sticky notes with step-by-step instructions, including how to get your Telegram chat ID and configure all integrations. How to Customize Adjust classification criteria**: Modify the AI Agent's system prompt to match your business type and lead qualification criteria Change notification format**: Edit the Telegram message template to include/exclude specific fields Add more actions**: Extend hot lead handling with additional nodes (e.g., add to CRM, send email, create task) Modify form fields**: Update field references if your JotForm uses different field names Multi-channel notifications**: Add Slack, Discord, or email notifications alongside Telegram Note All API keys and credentials shown in the workflow are placeholders. You'll need to replace them with your own credentials during setup.

Workflow explaination: https://youtu.be/ecafBTFPuvE?si=7csA1yNsaUxUG72F This workflow is designed to automatically handle new freelance project requests from a JotForm, analyze the requirements using AI, create a custom proposal, log the details in a Google Sheet, and send a personalized response to the client. 1. JotForm Trigger Purpose**: This node is the entry point of the entire automation. It waits for a new freelance project submission from your specified JotForm. Action: When a potential client fills out and submits the form, this node **instantly triggers the workflow, passing all submitted data (name, email, project requirements, and budget) to the next node. Key Detail**: Uses a webhook for real-time activation, ensuring immediate processing of every new project request. 2. AI Agent Purpose**: The central brain of your freelance workflow. 🧠 It takes the project submission and turns it into a structured, customized proposal. Action**: The agent follows a prompt sequence to perform these tasks: Calls the My Freelance Document Tool: Fetches your Google Doc containing details about your services, pricing, and project templates — your “source of truth.” Analyzes the Project Request: Reads the client’s requirements and goals from the form. Generates a Custom Proposal: Based on scope, budget, and relevance to your offerings, it prepares a short, tailored proposal or quote that fits the project. Creates a Personalized Email: Builds an HTML email with the proposal embedded, including next steps or a scheduling link for further discussion. Outputs Structured Data: Packages everything (project summary, proposal text, email subject, and body) into a clean JSON object for downstream use. 3. Append or Update Row in Sheet (Google Sheets) Purpose**: Serves as your lightweight CRM for all project inquiries. Action**: Logs data from the AI Agent (proposal details, client info, and project summary) into a Google Sheet. Key Detail: Configured to **Append or Update—if an email already exists, it updates that row instead of duplicating. Keeps your client records clean and organized. 4. If Purpose**: Acts as a control node to decide whether a proposal email should be sent. Action**: Checks the output from the AI Agent to ensure the proposal text is valid (not empty). Key Detail**: If the proposal generation fails or returns “NAN,” the workflow stops here to avoid sending incomplete responses. 5. Send a Message (Gmail) Purpose**: Sends the final personalized proposal email to the client. Action: Pulls the recipient’s email from the sheet and sends the **AI-generated subject and HTML proposal email automatically. Key Detail**: The email is customized per project, giving the client an instant, professional response with no manual effort.

AI-Powered Fake Review Detection Workflow Using n8n & Airtable This workflow automates the detection of potentially fake or manipulated product reviews using n8n, Airtable, OpenAI and Slack. It fetches reviews for a given product, standardizes the data, generates a unique hash to avoid duplicates, analyzes each review using an AI model, updates the record in Airtable and alerts the moderation team if the review appears suspicious. Quick Implementation Steps Add Airtable, OpenAI and Slack credentials to n8n. Create an Airtable Base with a reviews table. Connect the Webhook URL to your scraper or send sample JSON via Postman. Test the workflow by passing product and review URLs. Activate the workflow for continuous automated review screening. What It Does This workflow provides an automated pipeline to analyze product reviews and determine whether they may be fake or manipulated. It begins with a webhook that accepts product information and a scraper API URL. Using this information, the workflow fetches associated reviews. Each review is then expanded into separate items and normalized to maintain a consistent structure. The workflow generates a hash for deduplication, preventing multiple entries of the same review. New reviews are stored in Airtable and subsequently analyzed by OpenAI. The resulting risk score, explanation and classification are saved back into Airtable. If a review's score exceeds a predefined threshold, a structured Slack alert is sent to the moderation team. This ensures that high-risk reviews are escalated promptly while low-risk reviews are simply stored for recordkeeping. Who’s It For eCommerce marketplaces monitoring review integrity Sellers seeking automated fraud detection for product reviews SaaS platforms that accept user-generated reviews Trust & Safety and compliance teams Developers looking for an automated review-quality pipeline Requirements n8n (Cloud or Self-Hosted) Airtable Personal Access Token OpenAI API Key Slack Bot Token or Webhook Review Scraper API Basic understanding of Airtable field setup How It Works & How To Set Up 1. Receive Product Data The workflow starts with the Webhook – Receive Product Payload, which accepts a list of products and their scraper URLs. 2. Extract and Process Each Product Extract products separates the list into individual items. Process Each Product ensures that each product’s reviews are processed one at a time. 3. Fetch and Validate Reviews Fetch Product Reviews calls the scraper API. IF – Has Reviews? determines whether any reviews were returned. 4. Expand and Normalize Reviews Expand reviews[] to items splits reviews into individual items. Prepare Review Fields ensures consistent review structure. 5. Generate Review Hash Generate Review Hash1 produces a deterministic hash based on review text, reviewer ID, and date. 6. Airtable Deduplication Check Search Records by Hash checks whether the review already exists. Normalize Airtable Result cleans Airtable’s inconsistent empty output. Is New Review? decides if the review should be inserted or skipped. 7. Store New Reviews Create Review Record inserts new reviews into Airtable. 8. AI-Based Fake Review Analysis AI Fake Review Analysis sends relevant review fields to OpenAI. Parse AI Response ensures the output is valid JSON. 9. Update Airtable With AI Results Update Review Record stores the AI’s score, classification, and reasoning. 10. Moderation Alert Check Suspicious Score Threshold evaluates if the fake score exceeds a defined limit. If so, Send Moderation Alert posts a detailed message to Slack. How To Customize Nodes Fake Score Threshold Modify threshold in Check Suspicious Score Threshold. Slack Message Format Adjust text fields in Send Moderation Alert. AI Prompt Instructions Edit the instructions inside AI Fake Review Analysis. Airtable Fields Update mappings in both Create Review Record and Update Review Record. Additional Checks Insert enrichment steps before AI analysis, such as: reviewer profile metadata geolocation or reverse IP checks keyword density analysis Add-ons Notion integration for long-term review case tracking Jira or Trello integration for incident management Automated sentiment tagging Weekly review-risk summary reports Google Sheets backup for archived reviews Reviewer behavior modeling (number of reviews, frequency, patterns) Use Case Examples Detecting manipulated Amazon product reviews. Flagging repetitive or bot-like reviews for Shopify stores. Screening mobile app reviews for suspicious content. Quality-checking user reviews on multi-vendor marketplaces. Monitoring competitor-driven false negative or positive reviews. There can be many more scenarios where this workflow helps identify misleading product reviews. Troubleshooting Guide | Issue | Possible Cause | Solution | | ---------------------------- | ----------------------------------- | ------------------------------------------------------ | | No data after review fetch | Scraper API returned empty response | Validate scraper URL and structure | | Duplicate reviews inserted | Hash mismatch | Ensure Generate Review Hash1 uses the correct fields | | Slack alert not triggered | Bot not added to channel | Add bot to the target Slack channel | | AI response fails to parse | Model returned non-JSON response | Strengthen "JSON only" prompt in AI analysis | | Airtable search inconsistent | Airtable returns empty objects | Rely on Normalize Airtable Result for correction | Need Help If you need assistance customizing this workflow, integrating additional systems or designing advanced review moderation solutions, our n8n workflow development team at WeblineIndia is available to help. We offer support for: Workflow setup and scaling Custom automation logic AI-driven enhancements Integration with third-party platforms And so much more. Feel free to contact us for guidance, implementation or to build similar automated systems tailored to your needs.

Description Automates monitoring of error logs and notifies developers of critical errors. Sends Slack alerts for critical and non-critical errors, with auto-creation of Jira tickets for critical issues. Essential Information Triggers manually or on a scheduled basis (e.g., every 5 minutes). Reads and parses server logs to detect errors. Alerts developers via Slack and creates Jira tickets for critical errors. System Architecture Error Detection Pipeline**: Manual Trigger: Initiates the workflow manually. Schedule Every 5min: Schedules automatic runs every 5 minutes. Set Config: Configures basic parameters for log reading. Read Error Logs: Executes SSH command to fetch server logs. Wait For All Logs: Ensures all logs are read. Error Processing Flow**: Parse Logs: Parses logs and categorizes critical vs. non-critical errors. IF Critical Error: Filters for critical errors. Alert and Ticket Creation**: Send Slack Alert: Sends detailed alerts for critical errors via Slack. Create Jira Ticket: Creates a Jira ticket for critical errors. Send Non-Critical Alert: Sends simple alerts for non-critical errors via Slack. Implementation Guide Import the workflow JSON into n8n. Configure SSH credentials for log access. Set up Slack and Jira integrations with appropriate credentials. Test with a manual trigger and sample log data. Adjust the schedule (e.g., every 5min) and error parsing rules as needed. Monitor alert accuracy and ticket creation. Technical Dependencies SSH access for reading server logs. Slack API for team notifications. Jira API for bug ticket creation. n8n for workflow automation and scheduling. Customization Possibilities Adjust the Cron schedule for different intervals (e.g., every 10min). Modify Parse Logs node to refine error categorization rules. Customize Slack alert messages in Send Slack Alert and Send Non-Critical Alert nodes. Enhance Jira ticket details in Create Jira Ticket node (e.g., add priority). Add email notifications for additional alert channels.