The flow
Starts it 1Logic 10Service 3
The steps in the order they run, from what starts it.
- 1Daily Revenue Spike MonitorSchedule triggerStarts it
- 2Fetch WooCommerce OrdersWoo CommerceService
- 3Filter Paid Orders (Completed / Processing)FilterLogic
- 4 Filter Paid Orders (Completed / Processing)FilterLogic
- 5Filter Orders from Last 24 HoursCodeLogic
- 6Filter Orders from Last 24 Hours2CodeLogic
- 7Calculate Top Products (24h)CodeLogic
- 8Calculate Total Revenue (24h)CodeLogic
- 9Calculate Cancelled Metrics (24h)CodeLogic
- 10MergeMergeLogic
- 11Format Sales DataCodeLogic
- 12Revenue Spike Threshold CheckIfLogic
- 13Send Slack Sales Spike AlertSlackService
- 14Progress Alert (Target Pending)SlackService
How it's built
- Starts on
- A clock
- Steps
- 14, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Slack, WooCommerce
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Slack and WooCommerce accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 14 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 14 steps before you point it at anything that matters.