1. Opening Problem Statement
Meet Sarah, a small business owner running an online store via WooCommerce. Every time her customers place orders, Sarah has to manually check WooCommerce for new sales, especially for higher-value orders. This task is not only time-consuming but prone to errors—she often misses important notifications about key orders over $100, causing delays in processing and sometimes losing valuable customers’ trust. Sarah wastes hours daily toggling between WooCommerce and her team’s communication channels trying to keep everyone up-to-date.
Wouldn’t it be great for Sarah to receive instant alerts in Slack whenever a significant order is created, without any manual effort? That’s precisely the problem this n8n automation solves.
2. What This Automation Does
When this workflow runs, it continuously listens for new WooCommerce orders and automatically notifies your Slack channel, but only if the order total is above $100. Here’s what it does in detail:
- Monitors WooCommerce order creation events in real-time using the WooCommerce Trigger node.
- Checks the order total with an If node to ensure it meets the $100 threshold.
- Sends a formatted message to a designated Slack channel for all qualifying orders with key details like order ID, status, total amount, order link, order date, and transaction ID.
- Helps the sales and customer service team respond quickly to high-value orders without logging into WooCommerce manually.
- Reduces missed notifications and speeds up order processing, ensuring better customer satisfaction.
This automation can save Sarah up to an hour daily by eliminating manual checking and keeps her team instantly informed.
3. Prerequisites ⚙️
- WooCommerce account ⚙️ with API access credentials configured for n8n
- Slack workspace and API token 🔑 to send messages into a channel
- n8n automation platform account ⏱️, either cloud or self-hosted (consider hosting at Hostinger for easy setup)
4. Step-by-Step Guide
Step 1: Create a WooCommerce Trigger Node
In n8n, click + Add Node → Search and select WooCommerce Trigger.
Configure the node:
- Set the Event parameter to
order.createdto listen for new orders. - Choose your WooCommerce API credentials (you must have these set up previously).
You should see the node ready with a webhook configured, which n8n uses to receive order events.
Common mistake: Forgetting to set the API credentials or incorrectly setting the event type.
Step 2: Configure an If Node for Price Filtering
Add a new node: If.
Set its condition to:
- Number condition:
{{$json["total"]}} >= 100
This node ensures only orders with a total amount above or equal to $100 proceed to Slack.
Outputs: The true branch connects to Slack, and the false branch is left empty (no action).
Common mistake: Make sure to reference total correctly as it comes from WooCommerce order data.
Step 3: Add the Slack Node to Send Notifications
Add the Slack node.
Configure:
- Authorization: Connect your Slack API token.
- Set Channel to 700-commerce8 (or your own Slack channel name).
- Enter the notification text: “:sparkles: There is a new order :sparkles:” for quick alerts.
- Add Attachments with order details: Order ID, Status, Total, Link, Date Created, and Transaction ID. The values come dynamically from the WooCommerce JSON data, for example,
{{$json["id"]}}.
This structured alert message makes reading and responding to new orders easier.
Common mistake: Not mapping dynamic JSON variables correctly leads to missing data in Slack.
5. Customizations ✏️
- Change the Order Value Threshold: In the If node, adjust the condition
100to any other value based on your business needs. - Modify Slack Message Content: Edit the Slack node’s text or attachment fields to include more details like customer info or products ordered.
- Use Different Slack Channels: Change the channel field from
woo-commerceto any Slack channel your team uses for order alerts.
6. Troubleshooting 🔧
Problem: “No orders trigger the workflow”
Cause: WooCommerce webhook not set properly or API credentials wrong.
Solution: Verify WooCommerce webhook is active and credentials in n8n are correct under the WooCommerce Trigger node.
Problem: “Slack messages missing order details”
Cause: Incorrect JSON field references in Slack node attachments.
Solution: Double-check field mappings using expressions like {{$json["id"]}} and ensure the webhook data includes those fields.
7. Pre-Production Checklist ✅
- Test webhook in WooCommerce to confirm order.created events reach n8n.
- Simulate a test order above $100 to ensure Slack gets notified as expected.
- Check Slack channel permissions for the bot or token used.
- Verify correct API credentials on both WooCommerce and Slack nodes.
- Save and enable the workflow, then do a controlled test.
8. Deployment Guide
Activate the workflow in n8n by toggling it on after completing setup and testing.
Monitor n8n execution logs for any errors during live operation.
You can also set up alerts for n8n failures to ensure you don’t miss critical notifications.
9. FAQs
- Can I use other messaging platforms instead of Slack? Yes, you can replace the Slack node with others supported by n8n like Microsoft Teams or Discord by adjusting the message formatting.
- Does this consume a lot of API calls? Since it’s event-driven using webhooks, it’s very efficient, only triggering on new orders.
- Is my order data secure? Data flows securely within your n8n instance and Slack, but always review your API keys and permissions for best practices.
- Can it handle a high volume of orders? Yes, n8n scales well, but monitor execution times and node limits if needed.
10. Conclusion
By implementing this n8n workflow, you’ve automated the process of notifying your team in Slack whenever a new WooCommerce order above $100 is created. This saves you hours of manual checking each day and ensures faster response times to important orders. Over time, this will boost your customer satisfaction and improve your team’s workflow.
Next, you might want to expand automation to include inventory updates, customer feedback collection, or automated invoice generation using additional n8n nodes.
Let’s keep automating smarter, not harder!