10 n8n Automations Every Online Store Should Be Running

Running an online store means doing the same small tasks hundreds of times: checking new orders, chasing abandoned carts, updating spreadsheets, answering the same three customer questions. None of these tasks are hard. They are just constant, and constancy is what quietly eats your week.

n8n ecommerce automation fixes this in a way that off-the-shelf plugins rarely do. Because n8n is a visual workflow builder with a native WooCommerce Trigger node and hundreds of integrations, you can wire your store to your inbox, Slack, Google Sheets, and AI models exactly the way your business works, not the way a plugin vendor guessed you might.

One honest note before we start: store automations fire on every event: every order, every status change, every scheduled check. On cloud automation platforms with per-execution quotas, a moderately busy WooCommerce shop burns through its monthly allowance fast, and then you are either paying overage or your workflows silently stop. This is exactly the situation where how to self-host n8n becomes required reading, or where a managed option like Hosto n8n hosting makes sense: dedicated n8n VMs start at $9/mo billed annually with unlimited executions, so an order spike never becomes a billing spike.

Here are the ten workflows worth building first.

1. Abandoned-Cart Follow-Up Emails

What it does: Detects carts that were started but never checked out, waits a set period, then sends a recovery email.

Why it matters: Abandoned carts are the closest thing ecommerce has to money left on the table. The shopper already found you, chose products, and got most of the way through checkout. A timely reminder is the cheapest possible marketing message because the intent already exists: you are not creating demand, just removing friction from demand that stalled.

How it's wired: A Webhook node receives cart events from a WooCommerce cart-tracking plugin (or a Schedule Trigger polls pending orders via an HTTP Request node against the WooCommerce REST API). An IF node checks whether the cart is older than your threshold (say, two hours) and still unpaid. If true, a Gmail node (or Send Email node with your SMTP) fires a recovery message containing the cart contents and a checkout link. Add a second IF node to skip customers who already completed a different order in the meantime.

2. New-Order Alerts to Slack, Telegram, or WhatsApp

What it does: Posts a formatted message to your team channel the moment an order lands.

Why it matters: Fast awareness compounds. If your team sees orders in real time, packing starts sooner, problems (wrong address, weird quantity) get spotted before shipping, and everyone shares a visceral sense of how the store is doing without opening the admin dashboard.

How it's wired: A WooCommerce Trigger node listens for order.created. A Switch node routes by order total or product category: regular orders go to a Slack node posting in #orders, while wholesale or high-value orders also go to a Telegram node that pings the owner directly. For WhatsApp, an HTTP Request node calls the WhatsApp Business Cloud API with the order summary. The whole thing takes fifteen minutes to build and you will never turn it off.

3. Low-Stock Alerts Plus a Reorder Sheet

What it does: Watches inventory levels and maintains a live "reorder this" spreadsheet.

Why it matters: Stockouts are double damage: you lose the sale and you often lose the search ranking or ad momentum that product had. Catching low stock before it becomes no stock protects revenue you already earned the hard way.

How it's wired: A Schedule Trigger runs each morning. An HTTP Request node pulls products from the WooCommerce REST API (/wp-json/wc/v3/products with stock fields). An IF node filters items where stock has fallen below your reorder point. Matching products flow into a Google Sheets node that appends or updates rows in a reorder sheet: SKU, current stock, supplier, last order date. A Slack node posts a digest so someone actually looks at the sheet.

4. Automatic Order Log to Google Sheets or Accounting

What it does: Writes every completed order into a spreadsheet or accounting system, in real time, with the exact fields you care about.

Why it matters: Manual bookkeeping exports are where errors breed: a skipped week, a duplicated CSV, a mistyped refund. An always-on log means your accountant, your tax filings, and your gut-check revenue numbers all draw from the same automatically maintained source.

How it's wired: A WooCommerce Trigger node fires on order.updated. An IF node passes only orders whose status just became completed. A Google Sheets node appends a row: order ID, date, customer, line items, subtotal, tax, shipping, payment method. If you use a proper accounting tool, replace or supplement the sheet with an HTTP Request node calling its API to create an invoice. Refunds get a second branch via a Switch node so negative amounts land correctly.

5. Review-Request Emails N Days After Delivery

What it does: Sends a personal-feeling review request a fixed number of days after an order is marked complete.

Why it matters: Reviews are the highest-leverage content on your store because you don't write them and shoppers trust them more than anything you do write. The main reason customers don't leave reviews is that nobody asks at the right moment: after the product arrived, before the memory faded.

How it's wired: A Schedule Trigger runs daily. An HTTP Request node fetches orders completed exactly N days ago (seven is a sensible default for most physical goods). An IF node excludes orders that were refunded or already reviewed. A Gmail node sends a short, plain-text request naming the actual product and linking straight to its review form. Plain text matters here. It reads like a note from a human, not a campaign.

6. Failed-Payment Recovery Reminder

What it does: Notices orders stuck in failed or pending payment status and nudges the customer to retry.

Why it matters: A failed payment is usually not a lost customer: it's an expired card, a bank hiccup, or a 3-D Secure timeout. These shoppers decided to buy. Without a reminder, most will not come back on their own; with one, recovering even a handful per month is pure found revenue for zero marketing spend.

How it's wired: A WooCommerce Trigger node catches order.updated events. A Switch node routes on status: failed orders go straight to a Gmail node with a "your payment didn't go through, here's a retry link" message. Pending orders older than a few hours (checked with an IF node against the order date) get a gentler nudge. Add a Slack branch so your team sees repeat failures, which often indicate a checkout bug rather than a customer problem.

7. AI-Drafted Replies to Common Customer Emails

What it does: Reads incoming support emails, classifies them, and drafts a reply for you to approve, pulling real order data first.

Why it matters: Most store email is variations on five questions: where is my order, can I return this, do you ship to X, is this in stock, can I change my address. Drafting answers is not skilled work, but it interrupts skilled work constantly. Keeping a human on the final send preserves quality while removing ninety percent of the typing.

How it's wired: A Gmail node (trigger mode) watches your support inbox. An AI Agent node (or a simpler OpenAI node if you prefer a fixed prompt) classifies the message intent. For order-status questions, an HTTP Request node fetches the actual order and tracking state from WooCommerce so the model answers from real data instead of guessing. The drafted reply is saved back via a Gmail node as a draft, never auto-sent. A Switch node routes anything the model can't classify to a Slack node for human triage.

8. Daily Sales Summary Report to Your Inbox

What it does: Emails you a morning digest: yesterday's orders, revenue, refunds, top products, and anything anomalous.

Why it matters: Dashboards only work if you open them. A push report arrives whether or not you remembered to check, which means trends (a product suddenly selling, refunds creeping up) get noticed in days instead of weeks. It also ends the "let me just quickly check the store" habit that turns into forty minutes of admin-panel wandering.

How it's wired: A Schedule Trigger fires at 7 a.m. An HTTP Request node queries the WooCommerce reports endpoint for the previous day. An OpenAI node turns the raw JSON into three tight sentences of narrative ("Revenue was driven mostly by X; refunds were normal; stock on Y is getting thin"). A Gmail node delivers it. Optionally, a Google Sheets node appends the daily figures so you accumulate a history you own.

9. Syncing New Products to Social Channels and Feeds

What it does: When a product is published in WooCommerce, it's announced on your channels and pushed to your shopping feeds automatically.

Why it matters: Product launches have a consistency problem, not a creativity problem. The stores that seem "always active" on social media are usually just automated. Every product that never got posted is distribution you paid to create (photos, copy, inventory) and then didn't use.

How it's wired: A WooCommerce Trigger node fires on product.created. An OpenAI node drafts channel-appropriate copy from the product title, description, and price. HTTP Request nodes post to the Instagram Graph API and Facebook Pages API with the product image; a Telegram node announces to your channel or community. A parallel branch uses a Google Sheets node to maintain a product-feed sheet that Google Merchant Center ingests, so new items enter Shopping listings without manual feed edits.

10. Fraud and Big-Order Manual-Review Flag

What it does: Screens each new order against simple risk rules and holds suspicious ones for a human before fulfillment.

Why it matters: One fraudulent chargeback can wipe out the margin from dozens of legitimate orders: you lose the product, the shipping, and pay a chargeback fee. But blanket paranoia is worse: delaying every order to inspect it kills the fast-shipping experience. Automated triage gives you speed for the 98% and scrutiny for the rest.

How it's wired: A WooCommerce Trigger node fires on order.created. An IF node (or a Switch node for multiple tiers) checks rules you define: order total above a threshold, billing and shipping country mismatch, brand-new account with express shipping, multiple orders from one IP. Flagged orders trigger an HTTP Request node that sets the order status to on-hold via the WooCommerce API, plus a Slack node posting the details to a #review channel with a link to the order. Clean orders pass untouched: no added latency.

Where to Run All This

These ten workflows will collectively execute thousands of times a month on even a modest store. That's the point of them. If you're comparing infrastructure costs, our breakdown of WooCommerce hosting cost covers the store side; for the automation side, running your store and a dedicated n8n VM on one platform (as Hosto does) keeps latency low between WooCommerce webhooks and your workflows, and unlimited executions mean you design automations around what the business needs rather than what a quota allows.

Start with the new-order alert. It's the fifteen-minute win. Then build the abandoned-cart and failed-payment recoveries, because those pay for everything else.

FAQ

Do I need coding skills to build these WooCommerce automations in n8n?

No. Every workflow above uses standard nodes (WooCommerce Trigger, IF, Switch, Gmail, Slack, Google Sheets) connected visually. The only near-technical steps are generating WooCommerce REST API keys (two clicks in WooCommerce settings) and pasting endpoint URLs into HTTP Request nodes. If you can configure a WordPress plugin, you can build these.

Why not just use WooCommerce plugins for each of these tasks?

You can, but you'd be running ten separate plugins, each with its own settings screen, subscription fee, update cycle, and performance overhead on your storefront. n8n consolidates all of it into one tool running off your store server, so automations never slow down checkout. It's also composable: the same order data can feed Slack, Sheets, and your fraud rules from a single trigger.

How many n8n executions does a typical store actually use?

More than you'd guess. Every order fires several workflows (alert, log, fraud check), scheduled jobs run daily or hourly regardless of sales, and cart or email triggers fire on visitor behavior, not just purchases. A store doing a few hundred orders a month can easily generate several thousand executions. That's why per-execution cloud pricing gets uncomfortable quickly, and why self-hosted or dedicated n8n with unlimited executions is the standard recommendation for ecommerce.