Skip to main content

Monitor WooCommerce daily revenue spikes and send Slack alerts

Workflow preview

Workflow preview
100%
Monitor WooCommerce daily revenue spikes and send Slack alerts preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

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 d...

Best for

  • CRM automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.woocommerce, n8n-nodes-base.filter, n8n-nodes-base.code, n8n-nodes-base.scheduletrigger, n8n-nodes-base.if, n8n-nodes-base.slack, n8n-nodes-base.stickynote, n8n-nodes-base.merge

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by WeblineIndia.

Original n8n.io source

1.1 Workflow description

Title
Monitor WooCommerce daily revenue spikes and send Slack alerts
Workflow name
Monitor WooCommerce daily revenue spikes and send Slack alerts

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

  1. Schedule Trigger

    • Configure the Schedule Trigger to run once per day at your preferred time.
  2. Fetch Orders from WooCommerce

    • Use the WooCommerce node to retrieve recent orders from your store.
  3. Filter Paid Orders

    • Keep only orders with status Completed or Processing.
  4. Filter Last 24 Hours Orders

    • A Code node filters paid orders created within the last 24 hours.
  5. Calculate Top Products

    • A Code node aggregates product quantities sold in the last 24 hours.
  6. Calculate Total Revenue

    • A Code node calculates total revenue, order count, and average order value.
  7. 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.
  8. 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.
  9. Threshold Check

    • An IF node compares total revenue against a fixed threshold.
  10. 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.
  1. 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.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Fetch WooCommerce Orders

Type / Role
n8n-nodes-base.wooCommerce - wooCommerce
Config choices
Version 1

Block 2 - Filter Paid Orders (Completed / Processing)

Type / Role
n8n-nodes-base.filter - filter
Config choices
Version 2.2

Block 3 - Filter Orders from Last 24 Hours

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 4 - Calculate Total Revenue (24h)

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 5 - Daily Revenue Spike Monitor

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.2

Block 6 - Revenue Spike Threshold Check

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 7 - Send Slack Sales Spike Alert

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.3

Block 8 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 9 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 10 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 11 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 12 - Merge

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 13 - Calculate Top Products (24h)

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 14 - Format Sales Data

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 15 - Progress Alert (Target Pending)

Type / Role
n8n-nodes-base.slack - slack
Config choices
Version 2.3

Block 16 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 17 - Filter Orders from Last 24 Hours2

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 18 - Calculate Cancelled Metrics (24h)

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 19 - Sticky Note5

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 20 - Filter Paid Orders (Completed / Processing)

Type / Role
n8n-nodes-base.filter - filter
Config choices
Version 2.2

3. Summary Table

Workflow Monitor WooCommerce daily revenue spikes and send Slack alerts
Complexity advanced
Nodes 20
Categories CRM
Author WeblineIndia
Published 23 Dec 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/12059/12059.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Monitor WooCommerce daily revenue spikes and send Slack alerts do?

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 d...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your CRM use case.