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
-
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
CompletedorProcessing.
- Keep only orders with status
-
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.
- A separate WooCommerce branch fetches orders with status
-
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.
n8n WooCommerce Daily Revenue Spike Monitor and Slack Alerts
This n8n workflow monitors your WooCommerce store's daily revenue, identifies significant spikes compared to the previous day, and sends a Slack alert if a predefined threshold is exceeded. This helps you stay on top of unusual sales activity and react quickly to trends or issues.
What it does
- Schedules Daily Check: The workflow runs automatically every day (e.g., at 9 AM).
- Fetches WooCommerce Orders: It retrieves all WooCommerce orders from the previous day.
- Calculates Previous Day's Revenue: It processes the retrieved orders to sum up the total revenue for the previous day.
- Fetches WooCommerce Orders (Day Before): It then retrieves all WooCommerce orders from the day before the previous day.
- Calculates Day Before's Revenue: It processes these orders to sum up the total revenue for the day before the previous day.
- Calculates Revenue Difference: It computes the percentage difference between the previous day's revenue and the day before's revenue.
- Filters for Spikes: It checks if the calculated revenue spike exceeds a predefined percentage threshold (e.g., 50%).
- Sends Slack Alert: If a revenue spike is detected, it sends a detailed alert message to a specified Slack channel, including the revenue figures and the percentage increase.
Prerequisites/Requirements
- n8n Instance: A running n8n instance (cloud or self-hosted).
- WooCommerce Account: Access to your WooCommerce store with API credentials (Consumer Key and Consumer Secret).
- Slack Account: A Slack workspace and a channel where you want to receive alerts. You'll need a Slack API token or a Webhook URL.
Setup/Usage
- Import the workflow:
- Copy the provided JSON code.
- In your n8n instance, go to "Workflows" and click "New".
- Click the "Import from JSON" button and paste the workflow JSON.
- Configure Credentials:
- WooCommerce: Locate the "WooCommerce" nodes. You will need to create or select an existing WooCommerce credential. Provide your store URL, Consumer Key, and Consumer Secret.
- Slack: Locate the "Slack" node. Create or select an existing Slack credential. You can use an "OAuth" credential (recommended) or a "Webhook URL".
- Adjust Schedule (Optional):
- The "Schedule Trigger" node is configured to run daily. You can adjust the "Mode" and "Time" settings to fit your desired schedule.
- Adjust Spike Threshold (Optional):
- The "If" node (named "If") contains the logic for detecting a revenue spike. You can modify the condition to change the percentage increase threshold that triggers an alert. For example, change
item.json.revenue_spike_percentage > 50to a different percentage.
- The "If" node (named "If") contains the logic for detecting a revenue spike. You can modify the condition to change the percentage increase threshold that triggers an alert. For example, change
- Activate the Workflow:
- Once configured, make sure to activate the workflow by toggling the "Active" switch in the top right corner of the workflow editor.
This workflow provides a proactive way to monitor your WooCommerce store's performance and quickly identify significant revenue changes.
Related Templates
Track competitor SEO keywords with Decodo + GPT-4.1-mini + Google Sheets
This workflow automates competitor keyword research using OpenAI LLM and Decodo for intelligent web scraping. Who this is for SEO specialists, content strategists, and growth marketers who want to automate keyword research and competitive intelligence. Marketing analysts managing multiple clients or websites who need consistent SEO tracking without manual data pulls. Agencies or automation engineers using Google Sheets as an SEO data dashboard for keyword monitoring and reporting. What problem this workflow solves Tracking competitor keywords manually is slow and inconsistent. Most SEO tools provide limited API access or lack contextual keyword analysis. This workflow solves that by: Automatically scraping any competitor’s webpage with Decodo. Using OpenAI GPT-4.1-mini to interpret keyword intent, density, and semantic focus. Storing structured keyword insights directly in Google Sheets for ongoing tracking and trend analysis. What this workflow does Trigger — Manually start the workflow or schedule it to run periodically. Input Setup — Define the website URL and target country (e.g., https://dev.to, france). Data Scraping (Decodo) — Fetch competitor web content and metadata. Keyword Analysis (OpenAI GPT-4.1-mini) Extract primary and secondary keywords. Identify focus topics and semantic entities. Generate a keyword density summary and SEO strength score. Recommend optimization and internal linking opportunities. Data Structuring — Clean and convert GPT output into JSON format. Data Storage (Google Sheets) — Append structured keyword data to a Google Sheet for long-term tracking. Setup Prerequisites If you are new to Decode, please signup on this link visit.decodo.com n8n account with workflow editor access Decodo API credentials OpenAI API key Google Sheets account connected via OAuth2 Make sure to install the Decodo Community node. Create a Google Sheet Add columns for: primarykeywords, seostrengthscore, keyworddensity_summary, etc. Share with your n8n Google account. Connect Credentials Add credentials for: Decodo API credentials - You need to register, login and obtain the Basic Authentication Token via Decodo Dashboard OpenAI API (for GPT-4o-mini) Google Sheets OAuth2 Configure Input Fields Edit the “Set Input Fields” node to set your target site and region. Run the Workflow Click Execute Workflow in n8n. View structured results in your connected Google Sheet. How to customize this workflow Track Multiple Competitors → Use a Google Sheet or CSV list of URLs; loop through them using the Split In Batches node. Add Language Detection → Add a Gemini or GPT node before keyword analysis to detect content language and adjust prompts. Enhance the SEO Report → Expand the GPT prompt to include backlink insights, metadata optimization, or readability checks. Integrate Visualization → Connect your Google Sheet to Looker Studio for SEO performance dashboards. Schedule Auto-Runs → Use the Cron Node to run weekly or monthly for competitor keyword refreshes. Summary This workflow automates competitor keyword research using: Decodo for intelligent web scraping OpenAI GPT-4.1-mini for keyword and SEO analysis Google Sheets for live tracking and reporting It’s a complete AI-powered SEO intelligence pipeline ideal for teams that want actionable insights on keyword gaps, optimization opportunities, and content focus trends, without relying on expensive SEO SaaS tools.
Generate song lyrics and music from text prompts using OpenAI and Fal.ai Minimax
Spark your creativity instantly in any chat—turn a simple prompt like "heartbreak ballad" into original, full-length lyrics and a professional AI-generated music track, all without leaving your conversation. 📋 What This Template Does This chat-triggered workflow harnesses AI to generate detailed, genre-matched song lyrics (at least 600 characters) from user messages, then queues them for music synthesis via Fal.ai's minimax-music model. It polls asynchronously until the track is ready, delivering lyrics and audio URL back in chat. Crafts original, structured lyrics with verses, choruses, and bridges using OpenAI Submits to Fal.ai for melody, instrumentation, and vocals aligned to the style Handles long-running generations with smart looping and status checks Returns complete song package (lyrics + audio link) for seamless sharing 🔧 Prerequisites n8n account (self-hosted or cloud with chat integration enabled) OpenAI account with API access for GPT models Fal.ai account for AI music generation 🔑 Required Credentials OpenAI API Setup Go to platform.openai.com → API keys (sidebar) Click "Create new secret key" → Name it (e.g., "n8n Songwriter") Copy the key and add to n8n as "OpenAI API" credential type Test by sending a simple chat completion request Fal.ai HTTP Header Auth Setup Sign up at fal.ai → Dashboard → API Keys Generate a new API key → Copy it In n8n, create "HTTP Header Auth" credential: Name="Fal.ai", Header Name="Authorization", Header Value="Key [Your API Key]" Test with a simple GET to their queue endpoint (e.g., /status) ⚙️ Configuration Steps Import the workflow JSON into your n8n instance Assign OpenAI API credentials to the "OpenAI Chat Model" node Assign Fal.ai HTTP Header Auth to the "Generate Music Track", "Check Generation Status", and "Fetch Final Result" nodes Activate the workflow—chat trigger will appear in your n8n chat interface Test by messaging: "Create an upbeat pop song about road trips" 🎯 Use Cases Content Creators: YouTubers generating custom jingles for videos on the fly, streamlining production from idea to audio export Educators: Music teachers using chat prompts to create era-specific folk tunes for classroom discussions, fostering interactive learning Gift Personalization: Friends crafting anniversary R&B tracks from shared memories via quick chats, delivering emotional audio surprises Artist Brainstorming: Songwriters prototyping hip-hop beats in real-time during sessions, accelerating collaboration and iteration ⚠️ Troubleshooting Invalid JSON from AI Agent: Ensure the system prompt stresses valid JSON; test the agent standalone with a sample query Music Generation Fails (401/403): Verify Fal.ai API key has minimax-music access; check usage quotas in dashboard Status Polling Loops Indefinitely: Bump wait time to 45-60s for complex tracks; inspect fal.ai queue logs for bottlenecks Lyrics Under 600 Characters: Tweak agent prompt to enforce fuller structures like [V1][C][V2][B][C]; verify output length in executions
Automate Dutch Public Procurement Data Collection with TenderNed
TenderNed Public Procurement What This Workflow Does This workflow automates the collection of public procurement data from TenderNed (the official Dutch tender platform). It: Fetches the latest tender publications from the TenderNed API Retrieves detailed information in both XML and JSON formats for each tender Parses and extracts key information like organization names, titles, descriptions, and reference numbers Filters results based on your custom criteria Stores the data in a database for easy querying and analysis Setup Instructions This template comes with sticky notes providing step-by-step instructions in Dutch and various query options you can customize. Prerequisites TenderNed API Access - Register at TenderNed for API credentials Configuration Steps Set up TenderNed credentials: Add HTTP Basic Auth credentials with your TenderNed API username and password Apply these credentials to the three HTTP Request nodes: "Tenderned Publicaties" "Haal XML Details" "Haal JSON Details" Customize filters: Modify the "Filter op ..." node to match your specific requirements Examples: specific organizations, contract values, regions, etc. How It Works Step 1: Trigger The workflow can be triggered either manually for testing or automatically on a daily schedule. Step 2: Fetch Publications Makes an API call to TenderNed to retrieve a list of recent publications (up to 100 per request). Step 3: Process & Split Extracts the tender array from the response and splits it into individual items for processing. Step 4: Fetch Details For each tender, the workflow makes two parallel API calls: XML endpoint - Retrieves the complete tender documentation in XML format JSON endpoint - Fetches metadata including reference numbers and keywords Step 5: Parse & Merge Parses the XML data and merges it with the JSON metadata and batch information into a single data structure. Step 6: Extract Fields Maps the raw API data to clean, structured fields including: Publication ID and date Organization name Tender title and description Reference numbers (kenmerk, TED number) Step 7: Filter Applies your custom filter criteria to focus on relevant tenders only. Step 8: Store Inserts the processed data into your database for storage and future analysis. Customization Tips Modify API Parameters In the "Tenderned Publicaties" node, you can adjust: offset: Starting position for pagination size: Number of results per request (max 100) Add query parameters for date ranges, status filters, etc. Add More Fields Extend the "Splits Alle Velden" node to extract additional fields from the XML/JSON data, such as: Contract value estimates Deadline dates CPV codes (procurement classification) Contact information Integrate Notifications Add a Slack, Email, or Discord node after the filter to get notified about new matching tenders. Incremental Updates Modify the workflow to only fetch new tenders by: Storing the last execution timestamp Adding date filters to the API query Only processing publications newer than the last run Troubleshooting No data returned? Verify your TenderNed API credentials are correct Check that you have setup youre filter proper Need help setting this up or interested in a complete tender analysis solution? Get in touch 🔗 LinkedIn – Wessel Bulte