Workflow Templates

Chat-Based AWS Lambda Manager with Automated Audit Logging (GPT-4.1 mini + Google Sheet) > This workflow provides a chat-based AI agent to manage AWS Lambda functions. It allows users to list, invoke, get details, and delete Lambda functions, while automatically recording every action into Google Sheets for audit and compliance tracking. Who’s it for Cloud engineers and DevOps teams managing AWS Lambda functions. Developers who want a simple chat interface to perform Lambda operations. Compliance and operations teams needing automatic audit logs of AWS actions. How it works / What it does A chat message triggers the AWS Lambda Manager Agent. The agent interprets user intent and calls one of the available tools: Invoke Lambda Function: Runs a Lambda function with given payload. List Lambda Functions: Shows all functions in the account. Get Lambda Function: Retrieves details/configuration of a function. Delete a Function: Removes a Lambda function permanently. After each action, the agent calls Audit Logs (Google Sheets) to record the operation type, function name, timestamp, and outcome. The agent confirms destructive actions (like delete) before execution. How to set up Add a Chat Trigger node to start the workflow when a user sends a message. Connect it to the AWS Lambda Manager Agent node. Configure the agent with the provided system prompt to enforce rules and logging. Link the agent to the following tool nodes: Invoke Lambda Function List Lambda Functions Get Lambda Function Delete a Function Audit Logs (Google Sheets with appendOrUpdate enabled) Deploy the workflow and test it with sample chat commands like “list functions” or “invoke testFunction”. Requirements AWS account with IAM credentials that have lambda:ListFunctions, lambda:InvokeFunction, lambda:GetFunction, and lambda:DeleteFunction permissions. Google Sheets API connected for storing audit logs. Proper region and function names configured when invoking or deleting. n8n instance or automation platform that supports agent + tool integration. How to customize the workflow Add new tools**: Extend with more AWS Lambda operations like Update Function Code or Publish Version. Enhance logging**: Include user ID, request payload, or execution results in Audit Logs. Access control**: Restrict delete actions to admins by adding role-based logic. Multi-cloud support**: Extend the agent to handle Azure/AWS/GCP serverless functions in one workflow. Custom responses**: Modify agent prompt to tailor tone (developer-friendly vs. business-friendly).

> ⚠️ Multi-language Slack Error Notifier Track errors like a pro — this prebuilt Slack alert flow notifies you instantly when any workflow fails. ✅ No coding needed ✅ Works with any workflow via Error Workflow setting ✅ Step-by-step setup guides in: 🇬🇧 English 🇪🇸 Español 🇩🇪 Deutsch 🇫🇷 Français 🇷🇺 Русский Just plug it in, follow the quick setup, and never miss a failure again.

📄 Zoho CRM Change Tracking & Automated Suspicious Activity Alerts Workflow This n8n workflow automatically monitors selected Zoho CRM modules for record changes, identifies suspicious modification patterns, logs all activity into a Google Sheet, generates an audit JSON file for each record and sends immediate email alerts for suspicious events. It runs incrementally using a time window so only recent changes are processed, keeping monitoring continuous and accurate. ⚡ Quick Start — “Implement in 5 Steps” Import the workflow JSON into n8n. Connect credentials: Zoho CRM OAuth2, Gmail OAuth2, Google Sheets. Update Google Sheet ID + recipient email if needed. Review modules being monitored (Leads, Contacts, Accounts, Deals). Activate the workflow — n8n begins tracking CRM changes instantly. What It Does This workflow acts as an automated security and audit layer for Zoho CRM. It fetches updated records from selected CRM modules within a calculated time window, extracts critical change details, and enriches them with timestamps, ownership, field change counts, and metadata. Based on defined rules, it identifies unusual or high-risk patterns such as deletions, ownership updates, email modifications or bulk field changes. Every record that is processed is output in two ways: Structured logging** into a Google Sheet (appended or updated). Binary JSON audit file** generated for robust audit storage. When suspicious patterns are detected, the workflow immediately generates a rich HTML email alert to your security team, ensuring fast response. The lastRun value is maintained to avoid duplicate processing. Who’s It For This workflow is ideal for: CRM Administrators** needing automated monitoring. Security Teams** tracking unauthorized modifications. Data Compliance Officers** requiring audit trails. Organizations with high CRM usage**, especially sales operations. Teams looking to automate change logs without manual review.** Prerequisites To run this workflow successfully, ensure you have: n8n instance** (cloud or self-hosted). Zoho CRM OAuth2 credentials** with access to modules & search APIs. Google Sheets OAuth2 credentials** + an existing sheet. Gmail OAuth2 credentials** for sending alerts. Correct timezone settings** in your CRM & workflow environment. Ability to edit function nodes if you need deeper customization. How to Use & Setup Step 1 — Import Workflow Upload the provided JSON file inside n8n. Step 2 — Connect Credentials Configure nodes: Zoho List Modules → Zoho OAuth2 Zoho Search (module) → Zoho OAuth2 Append or update row in sheet → Google Sheets Email Security Team → Gmail OAuth2 Step 3 — Setup Google Sheet Your sheet should contain at least these columns: Timestamp Record Id Module Field Changes Count Is Suspicious Company Name Email User Name Update the sheet ID in the node if needed. Step 4 — Validate Modules List By default, the workflow monitors: Leads Contacts Accounts Deals This is defined in two nodes: Modules list (from API) and Filter unsupported modules. Step 5 — Activate Workflow Once activated, it calculates a time window using: The last successful run (lastRun) Current timestamp A polling range of 5 minutes Only changes within this window are processed. How To Customize Nodes 1. Compute Time Window Modify polling time via pollMinutes = 5 if desired. The node stores lastRun so it never processes duplicate events. 2. Modules list (from API) Update the requiredModule array to include or remove CRM modules. 3. Suspicious Logic (as implemented) In Detect Unusual Patterns, a record is flagged suspicious if: The event contains "delete" Changed fields include: owner, assigned_to, owner_id email, contact_email role, is_admin, profile More than 10 fields were modified in one update Reasons are stored in suspicious_reasons A boolean flag suspicious = true/false These rules can be modified directly inside the function code. 4. Email Template Edit subject, HTML body, or recipients in the Email Security Team (Gmail) node. 5. Google Sheets Mapping Column mapping can be modified or extended directly in the Append or update row node. Add-Ons (Optional Enhancements) These Add-Ons align strictly with the workflow’s existing structure: ✔ Add more Zoho CRM modules Expand requiredModule arrays in two function nodes. ✔ Adjust suspicious detection rules Customize keywords, field names, or thresholds in Detect Unusual Patterns. ✔ Add more fields to the Google Sheet Extend mapping in the Google Sheets node. ✔ Change alert recipients or message style Modify the Gmail node’s HTML and toList fields. ✔ Increase audit retention by storing JSON files Forward binary audits to Drive, Dropbox, or S3 using an additional node. Use Case Examples This workflow can support several practical business scenarios: Unauthorized Access Monitoring Detects if users modify sensitive fields like email, owner, or permissions. Mass Data Manipulation Alerts Spot bulk changes where more than 10 fields were modified at once. Sales Pipeline Integrity Checks Track Deal or Lead ownership changes that may affect reporting accuracy. Contact Data Security Email changes in Contacts or Leads are flagged immediately. Audit Log Maintenance Creates JSON audit files + logs in Google Sheets for compliance. There can be many more use cases depending on your CRM setup and security policies. Troubleshooting Guide | Issue | Possible Cause | Solution | | ---------------------------------- | -------------------------------------- | ------------------------------------------------------ | | No data being captured | Zoho OAuth issue or wrong modules list | Reconnect OAuth & verify module API names | | Suspicious emails not sent | Gmail OAuth not connected | Re-authenticate Gmail credentials | | Duplicate rows in Google Sheet | Matching column misconfigured | Check “Record Id” mapping in Google Sheet node | | Workflow processes too few records | Time window too small | Increase pollMinutes in Compute from/to | | Missing fields in Google Sheet | Mapping not defined | Extend mapping under Sheets → Columns | | Audit file not generated | Binary property overwritten | Ensure no node clears binary data before file creation | | Workflow doesn’t resume continuity | lastRun not updating | Check Update lastRun node execution path | Need Help? If you need assistance customizing: Suspicious logic Module lists Google Sheet structure Email templates Or building more advanced CRM security automations The n8n Team at WeblineIndia can help extend, optimize or deploy this workflow professionally. Feel free to reach out for setup, enhancements or complete automation solutions.

This automated n8n workflow monitors API uptime by periodically checking API availability and sending instant WhatsApp alerts if any service goes down. It retrieves API details from a Google Sheet and includes retry logic for failed requests. Good to Know Checks API status every 15 minutes Integrates with Google Sheets for API list management Implements a retry mechanism with up to 4 attempts Sends WhatsApp alerts for downtime Supports customizable API request configurations How It Works Schedule Trigger** - Triggers every 15 minutes Read API List** - Fetches all API URLs from a Google Sheet Process Each API1** - Loops through each API entry Init Retry Counter** - Initializes retryCount = 0 Test API** - Sends the first request to the API Check Response** - Checks if a valid response was received If No Response** - Branches into retry flow if down Wait 10 Min → Increment Retry → Retry API → Check Retry Response** - Wait and retry API call once If Still No Response** - Verifies if retry also failed If Still No Retry > 4** - Checks if retry limit is reached (≥ 4) Format Down Alert** - Formats the WhatsApp alert with API details Send WhatsApp Alert** - Sends API down alert to the configured number Continue Next API** - Moves to the next API in the list How to Use Import workflow into n8n Configure Google Sheets API for API list access Set up WhatsApp API for alerts Define API details in Google Sheet Test with sample APIs and verify alerts Adjust retry limits or schedule as needed Requirements Access to Google Sheets API WhatsApp API configuration Scheduled trigger setup in n8n Sheet Structure | Sheet Column | Example Data | | -------------------- | ------------------------------------------------------------ | | name | Timeout Test | | method | GET | | url | https://httpbin.org/delay/15 | | headers | {"Content-Type": "application/json"} | | body | {"key": "value"} | | expectedField | status | | expectedValue | success | | expectedStatusCode | 200 | Customizing This Workflow Modify trigger interval Adjust retry limits or wait times Customize WhatsApp alert format Add additional API headers or body data Integrate with other notification services

What this workflow does This template automates the entire process of documenting Sprint Reviews in Scrum: Input Collection – Through a friendly form, users upload the transcript file (meeting notes, sprint review transcript, or VTT captions) and specify the sprint name and domain. Transcript Parsing – A Code node formats the transcript into clean [HH:MM:SS] Speaker: text lines, supporting VTT, Zoom, or custom timestamp formats used in Scrum events. AI-Driven Summary – The AI Agent (LangChain + OpenAI) produces a well-structured AI summarization in Markdown, including: A 3–5 bullet Executive Summary of sprint review highlights A Presentation Recap table (Timestamp | Presenter | Topics) A list of Action Items with owners (if recognizable from the transcript) Preview – The summary renders as a styled card with custom CSS for easy readability in n8n. Archive – Automatically appends a record to Google Sheets, saving the date, domain, sprint, transcript file name, and the AI-generated sprint review summary. Why it’s useful Zero manual summarizing** – AI extracts key insights from transcript files into Markdown you can instantly share with your Scrum team and stakeholders. Easy setup** – drag-and-drop import, plus form-based input for non-technical users during sprint reviews. Centralized tracking** – all past sprint summaries live in one spreadsheet for retrospectives, audits, and continuous improvement. Flexible and extendable** – you can switch to Airtable, Slack, or Notion, or refine the summary template to match your Scrum workflow. Ideal for Scrum Masters** wanting quick sprint review summaries for stakeholders Agile Coaches** analyzing sprint review transcripts, presentation patterns, and follow-up tasks Product Owners** keeping a searchable log of sprint outcomes and action items Prerequisites / Credentials OpenAI API Key** — required for the AI Agent node (or any other Agent for summarization) Google Sheets OAuth2 credentials** — required for saving sprint review data to Sheets (Optional) Ensure LangChain / AI Agent nodes are installed in your n8n instance How to Use This Template Import the workflow JSON into your n8n instance. Set up credentials: For the OpenAI LLM node, provide your OpenAI API key In Google Sheets, configure OAuth2 and specify your spreadsheet ID (replace YOUR_SHEET_ID) Create a new sheet with the following columns: Date Domain Sprint name Content VTT file Transcript Enable and run the workflow. Fill out the form: upload transcript file, enter sprint & domain, click Create Summary. View the AI-generated Markdown sprint review summary in the preview card. Verify the new entry appears in your Google Sheet with all sprint details.

Spotify Music Downloader: Effortless Music Downloading from Spotify Description: The Spotify Music Downloader is an automation flow that allows users to easily download music from Spotify tracks. By leveraging the powerful Spotify Downloader API, the flow downloads Spotify tracks, uploads them to Google Drive, and logs the details to Google Sheets for better management. With this tool, you can save time and effort while enjoying the convenience of direct downloads and automatic organization. Use Case: Music Enthusiasts**: Easily download your favorite Spotify tracks and store them in Google Drive. Content Creators**: Automate the process of storing and tracking downloaded music files. Organizational Automation**: Store download links and file sizes in Google Sheets to track downloads systematically. Spotify Users**: Provides a hassle-free way to access and organize your Spotify music offline. Benefits: Simple & Automated**: Easily download and organize music from Spotify with minimal effort. Seamless Integration**: Directly integrates with Google Drive for storage and Google Sheets for tracking. Fast: Uses the **Spotify Downloader API to quickly fetch and download the tracks. Track Downloads**: Keep a record of each download, including size, download link, and other details. Google Drive Storage**: Automatic storage of downloaded tracks in your Google Drive, making it easy to access files anytime. Node-by-Node Explanation: On Form Submission: The flow starts when the user submits a Spotify track URL through a form. HTTP Request (Spotify Downloader API): Sends a request to the Spotify Downloader API to retrieve the music file associated with the given Spotify URL. If (Link Validation): Ensures that the provided Spotify URL is not empty. If1 (Success Validation): Checks if the API response was successful. Download Music: Downloads the music file from the provided Spotify link using the fetched download URL. Google Drive: Uploads the downloaded music file to Google Drive. Google Sheets: Logs the successful download details (like URL, download link, size, and timestamp) to Google Sheets. Code (File Size Calculation): Calculates the file size of the downloaded music file in MB. Wait: Introduces a delay to ensure that the upload process to Google Drive is complete before continuing. Wait1: Another wait node to allow additional time between the various steps in the flow. Google Sheets1 (Success Logs): Adds a new record for a successful download to a Google Sheet. Google Sheets2 (Failed Logs): Records failed download attempts in a secondary Google Sheet. By utilizing this flow, you can automate the process of downloading music from Spotify and storing it in Google Drive while keeping track of every download in Google Sheets. It's an ideal solution for music lovers, content creators, or anyone looking to automate their music download and storage process with ease. Create your free n8n account and set up the workflow in just a few minutes using the link below: 👉 Start Automating with n8n Save time, stay consistent, and grow your LinkedIn presence effortlessly!

Post Jobs to Multiple Boards from Google Sheets using BrowerAct This powerful n8n template turns a Google Sheet into a control panel for automating job postings across multiple job boards. This workflow is perfect for HR teams, recruiters, and hiring managers who want to streamline their hiring process by posting jobs to multiple boards from a single source of truth. Self-Hosted Only This Workflow uses a community contribution and is designed and tested for self-hosted n8n instances only. How it works The workflow is triggered in two ways: manually (to batch-post all "Ready to Post" jobs) or automatically via a Google Sheets Trigger when a single row is updated. An If node filters for jobs marked with the status 'Ready to Post'. A BrowserAct node takes the job details (title, description, logins, target URL) and runs an automation to post the job on the specified board. An If node checks if the posting was successful. If it fails, a Slack alert is sent. A Code node parses the successful result from BrowserAct to get the status and live URL. The workflow Updates the row in Google Sheets with the Live_URL and changes the Status to 'Posted'. A final Slack message is sent to a channel to confirm the successful posting. Requirements BrowserAct** API account for automated posting BrowserAct* "Automated Job Posting to Niche Job Site (Custom Site)*" Template | User needs to customize the workflow based on the target site. BrowserAct** n8n Community Node -> (n8n Nodes BrowserAct) Google Sheets** credentials Slack** credentials for sending notifications Need Help? How to Find Your BrowseAct API Key & Workflow ID How to Connect n8n to Browseract How to Use & Customize BrowserAct Templates How to Use the BrowserAct N8N Community Node

This workflow utilizes Philips IntelliVue Device details to automatically track patient vitals, such as heart rate and oxygen levels. It quickly spots critical health issues and sends alerts to healthcare staff for fast action. The system saves data for records and helps improve patient care with real-time updates. It’s simple to set up and adjust for different needs. Essential Information Processes data from Philips IntelliVue Devices to monitor vitals instantly. Filters and categorizes conditions as critical or non-critical based on thresholds. Sends clinical alerts for critical conditions and logs data for review. Runs every 30 seconds to ensure timely updates. System Architecture Data Collection Pipeline: Poll Device Data Every 30s**: Continuously retrieves vitals from Philips IntelliVue Devices. Fetch from IntelliVue Gateway**: Retrieves data via HTTP GET requests. Processing Pipeline: Process Device Data**: Analyzes and validates the data stream. Alert Generation Flow: Validate & Enrich Data**: Ensures accuracy and adds patient context. Save to Patient Database**: Stores data for records. Check Alert Status**: Applies rules to trigger alerts. Send Clinical Alert**: Notifies staff for critical conditions. Implementation Guide Import workflow JSON into n8n. Configure the Philips IntelliVue Devices gateway URL and test with sample data. Set up alert credentials (e.g., email). Test and adjust rule thresholds. Technical Dependencies Philips IntelliVue Devices for vitals data. n8n for automation. Email or messaging API for alerts. Database for data storage. Customization Possibilities Adjust Switch node rules for critical thresholds. Customize alert messages. Modify database schema. Add logging for analysis.

Description This workflow acts as a CI/CD-style test harness for validating other n8n workflows. It executes a target workflow (here: Archive Payment Receipts), evaluates pass/fail outcomes, and generates structured reports. Results are automatically archived to Google Drive, logged in Google Sheets, and synced with ClickUp for visibility. Both success and failure scenarios are handled with standardized formatting. What This Template Does (Step-by-Step) ⚡ Manual Trigger – Start the test run manually. ▶️ Execute Target Workflow Under Test – Calls the specified workflow (Archive Payment Receipts) and captures its output, even if it errors. ✅ Test Result Evaluation (If Node) – Checks if the output contains errors. Pass Path → success formatting + archival. Fail Path → failure formatting + logging. 📄 Format Success Test Result (Set Node) – Creates a structured result object with: Status: ✅ Passed Workflow Name Timestamp 📄 Format Failed Test Result (Set Node) – Same as above, but with ❌ Failed status. 📝 Generate Success/Failure Report Text (Code Node) – Converts structured data into a human-readable report string. 📦 Convert Report to Text File – Transforms the text into a .txt file for archiving. ☁️ Archive Reports to Google Drive – Saves .txt files (success/failure) into the resume store folder with timestamped filenames. ✏️ Update ClickUp Task (Success/Failure) – Posts results directly into a ClickUp task for visibility. 📊 Log Error Details to Error Tracking Sheet (Google Sheets) – Appends raw error objects to an error log sheet for debugging and trend analysis. Prerequisites Target workflow to test (e.g., Archive Payment Receipts) Google Drive folder for report storage Google Sheets (Error Log tab) ClickUp API credentials n8n instance Key Benefits ✅ Automates workflow regression testing ✅ Captures pass/fail outcomes with full audit trail ✅ Maintains error logs for debugging and reliability improvements ✅ Keeps stakeholders updated via ClickUp integration ✅ Supports compliance with archived test reports Perfect For Teams running workflow QA & testing Organizations needing audit-ready test reports DevOps pipelines with continuous validation of automations Stakeholders requiring real-time visibility into workflow health

Automated Trade Report from Interactive Brokers This workflow is aimed at traders who use Interactive Brokers. It automatically retrieves the trades made in IBKR on a daily basis and writes them to a Google Sheet, so that anyone can easily perform further analyses and statistics using the on-board tools. This creates an automatic, continuous trade journal. Typical Usecaes Monitoring your trades in one journal Analyze your Profit & Losses Basis for any kind of statistics • Log trades (entry, exit, setup, reason) • Analyze performance (win rate, R/R, expectancy) • Evaluate strategies & setups • Detect mistakes & patterns • Track emotions & discipline • Support coaching, reviews & improvement How it works A daily schedule triggers a FlexStatement request to Interactive Brokers to start generating a trade report. The workflow extracts the reference code from IBKR's response, waits for the report to be ready, then downloads the Flex report XML. The XML is parsed and split into individual Trade records. Key fields (tradeDate, symbol, quantity, buySell, tradeID, price, money, currency, fxRateToBase) are normalized.\n5. Each trade is appended or updated in the configured Google Sheet, matching on tradeID to avoid duplicates and keep the journal current. Prerequisites Trading Account on IBKR Google Sheets OAuth2 A Google Sheet containing your trading journal Setup [ ] Set schedule to run at your desired time (default: 08:00) [ ] Add or verify IBKR request token/reference parameters. 1. Create Flex Query Token: Go to IBKR Account Management Reports → Flex Queries → Flex Web Service → Generate Current Token → Make a note of the token (e.g.: 123456789012345678901234) 2. Enter Flex Token: In node '1. Request Flex Report' and in node '2. Extract Reference Code' Replace YOUR_FLEX_TOKEN with your token ID 3. Create Flex Query in IBKR (if not already done): Go to IBKR Account Management Reports → Flex Queries → Activity Flex Query → Create Select: Trade Confirmation ✓ Period: Last 365 Days Format: XML Save and note down the query ID 4. Enter Flex Query ID: In node '1. Request Flex Report' Replace YOUR_QUERY_ID with your query ID [ ] Adjust wait time if IBKR needs longer to generate reports [ ] Select the Google Sheet and target sheet/tab [ ] Connect Google Sheets OAuth2 account [ ] Confirm column mapping and that tradeID is the matching column [ ] Run a manual test to validate parsing and row updates

This weekly workflow automatically identifies new ranked keywords for your domain within Google’s top 10 results without manual SERP monitoring. On each run, the workflow fetches the latest ranking and search volume data using the DataForSEO Labs API and stores a fresh results snapshot in Airtable. It then compares this data with the previous set to identify any new keywords your domain started ranking for, focusing on queries that rank in the top 10. All newly ranked top-10 keywords are logged in Airtable, along with their ranking position and search volume. Once new terms and rankings are identified, the workflow sends you a Slack summary highlighting the latest changes. Who’s it for SEO experts and marketers who want an automated way to track new top-ranking keywords on Google for their domain(s). What it does This workflow automatically detects when your domain enters top-10 results for new keywords on Google, records them in Airtable, and sends a weekly summary via Slack. How it works Runs on a predefined schedule (default: weekly). Reads your keywords and target domains from Airtable. Fetches the latest Google rankings and keyword metrics via DataForSEO API. Compares the latest data with the previous run. Logs newly ranked top-10 keywords to Airtable. Sends a Slack summary with key changes. Requirements DataForSEO account and API credentials Airtable table with your keywords, following the required column structure. Airtable table with your target domains, following the required column structure. Slack account Customization You can easily customize this workflow by adjusting the run schedule, changing the minimum ranking threshold (e.g., top 5 or top 20), exporting results to other tools, and tailoring the Slack message content to your team’s workflow.

WooCommerce Daily Sales & Revenue Spike Monitor → Slack Alert This workflow automatically checks your WooCommerce store’s last 24 hours of revenue, top-selling products, and cancelled orders on a daily schedule. It sends Slack notifications when sales cross a defined threshold or provides a detailed status update—including cancellation impact—if the target hasn’t been met, helping teams react quickly without manual reporting. 🚀 Quick Implementation Steps Set up the Schedule Trigger to run daily Connect WooCommerce and fetch recent orders Filter paid and cancelled orders separately Filter both datasets to the last 24 hours Calculate revenue, top products, and cancellation impact Merge and format sales and cancellation data Compare revenue with a configurable threshold Send enriched Slack alerts with sales and cancellation insights What It Does This workflow serves as a daily sales and revenue health monitoring assistant for your WooCommerce store. It runs automatically on a schedule and collects recent order data from WooCommerce via API. Only paid orders (Completed / Processing) are considered for revenue calculations. Cancelled orders are processed in a separate branch to track revenue loss. Orders created within the last 24 hours are filtered for both paid and cancelled orders. The workflow calculates total revenue, order count, average order value, and top-selling products. It also calculates cancelled order count and cancelled revenue to highlight potential revenue leakage. Sales and cancellation data are merged into a single structured object. An IF node checks whether revenue exceeds a predefined threshold. If the threshold is crossed, a Slack Sales Spike Alert is sent with cancellation context. If the threshold is not reached, a Slack Status / Pending Alert is sent showing progress, top products, and cancellation impact—keeping the team informed without noise. Who’s It For Business owners monitoring daily sales and revenue health Sales and marketing teams tracking revenue spikes and losses E-commerce managers using WooCommerce Operations teams monitoring cancellations and fulfillment risks Non-technical users who want actionable insights without dashboards Requirements to Use This Workflow An active WooCommerce store WooCommerce REST API credentials** An n8n instance (cloud or self-hosted) A Slack workspace with incoming webhook or Slack credentials Permission to read WooCommerce orders and post Slack messages How It Works & Set Up Schedule Trigger Configure the Schedule Trigger to run once per day at your preferred time. Fetch Orders from WooCommerce Use the WooCommerce node to retrieve recent orders from your store. Filter Paid Orders Keep only orders with status Completed or Processing. Filter Last 24 Hours Orders A Code node filters paid orders created within the last 24 hours. Calculate Top Products A Code node aggregates product quantities sold in the last 24 hours. Calculate Total Revenue A Code node calculates total revenue, order count, and average order value. Fetch & Process Cancelled Orders A separate WooCommerce branch fetches orders with status Cancelled. Cancelled orders are filtered to the last 24 hours using a Code node. A Code node calculates cancelled order count and cancelled revenue. Merge & Format Sales Data A Merge node combines sales metrics and cancellation metrics. A Code node formats all results into a single JSON object for Slack. Threshold Check An IF node compares total revenue against a fixed threshold. Send Slack Alerts TRUE path: Sends a **Sales Spike Alert including revenue, top products, and cancellation impact. FALSE path: Sends a **Status / Pending Alert showing current performance, top products, and cancellation insights. Activate Workflow Test once and activate the workflow for daily monitoring. How To Customize Nodes Threshold Value**: Update the IF node condition to match your business target Schedule Time**: Change the Schedule Trigger execution time Slack Channels**: Update Slack nodes to post in your desired channels Order Status Logic**: Adjust filters for paid or cancelled orders if needed Time Window**: Modify the 24-hour logic to 12 hours, 48 hours, or weekly Cancellation Sensitivity**: Add conditions to alert on high cancellation volume or revenue impact Add-ons (Optional Enhancements) Add cancellation rate (%) and net revenue calculations Trigger alerts when cancellation revenue exceeds a defined percentage Store daily sales and cancellation history in Google Sheets or a database Add day-over-day or week-over-week comparisons Send alerts to Microsoft Teams or Email Attach a CSV report with order and cancellation details Use Case Examples Detect viral product sales quickly Monitor flash sale performance Identify revenue loss due to cancellations Alert leadership on high-revenue or high-risk days Track campaign-driven sales spikes and drop-offs Support inventory, operations, and customer experience planning > Many more business scenarios can be addressed based on your store’s needs. Troubleshooting Guide | Issue | Possible Cause | Solution | | ---------------------------------- | -------------------------------- | ---------------------------------------- | | No Slack alert received | Revenue did not exceed threshold | Check threshold or test with lower value | | Workflow fails | WooCommerce API error | Verify API credentials and permissions | | Revenue or cancellation shows zero | Orders filtered out | Validate order status and date logic | | Slack message not sent | Wrong Slack credentials | Reconnect Slack node | | Orders missing | Timezone mismatch | Align WooCommerce and n8n timezone | Need Help? Need help setting up this workflow or customizing it further? Our n8n workflow development team at WeblineIndia can assist you with implementation, add-ons, performance optimization and building similar n8n automations tailored to your business needs. 👉 Contact WeblineIndia today to automate smarter and scale faster.