Your store doesn’t stop when you close your laptop. Orders come in at 2 a.m., carts get abandoned on a Sunday, and a customer who should get a “your order shipped” text is instead finding out from the delivery driver. You didn’t build a WooCommerce store to spend your evenings doing the follow-up work a computer should be doing for you.
Quick answer: WooCommerce automation connects the events already happening in your store (a new order, an abandoned cart, a customer’s second purchase of the same product) to the actions you’d otherwise do by hand (send a message, update a sheet, alert your team). Below are seven automations that pay for themselves fast, grouped by what they actually protect: your visibility, your revenue, and your relationship with the customer after the sale.
Here’s the part most guides on this topic skip: most people who set out to automate their store never get past step one. We pulled our own onboarding numbers to find out why, and the answer wasn’t flattering. Of 19,815 stores that signed up specifically to build automations, only 13.7% ever ran one. Just 10.5% got one live on their actual store. That’s not a knock on the people who tried, it’s the reason this list looks the way it does. Every one of the seven below survived the same test: small enough to finish today, specific enough to show a result by tomorrow.
What “Automation” Actually Means for a WooCommerce Store
Every automation has three parts. A trigger is something that just happened, a new order, a product going out of stock, a subscription failing to renew. An action is what happens next, a message sent, a record updated, a task created. And the connection between them is the workflow you build once and never touch again.
You don’t need to understand any of that to use it. What’s worth understanding is where people actually stop. In that same signup data, 57.3% of stores connected an integration, meaning they got as far as linking WooCommerce to something else. Only 43.6% went on to build automation with it. That gap, connecting something and never building anything with it, is bigger than the gap between building one and running one. The seven workflows below are grouped by what they protect, so you can pick based on what’s actually costing you something, not just what sounds impressive.
A dedicated review-request plugin can do #6. A restock plugin can do part of #4. Neither one watches your Slack, your spreadsheet, and your subscription renewals at the same time, because neither was built to. That’s the actual case for one connected tool over six single-purpose ones: not that the single-purpose plugin does its one job worse, but that you’d be running six of them side by side to cover what one workflow builder does at once.
See What’s Happening the Moment It Happens
1. New Order → Team Alert, Before the Customer Has to Ask
The trigger: a new WooCommerce order. The action: an instant message to your team’s Slack or Telegram channel.
Most automation guides stop at “send a notification.” The order trigger itself now carries richer context than a bare number, enough that the message landing in Slack can include what was bought and who bought it, not just an order ID your team has to go look up in WordPress. Set the trigger once, and every order lands in front of a human immediately, with enough to act on it without opening the dashboard.
2. Order Data → A Live Spreadsheet, Without Anyone Copying and Pasting
The trigger: order placed or order status changed. The action: a new row in Google Sheets, or an update to an existing one.
This looks like the least exciting automation on this list, and it’s actually one of the most common starting points there is. Google Sheets ties for the fifth most-connected tool among first-time OttoKit integrations, right behind WordPress itself. That’s not a coincidence, it’s the automation that replaces the person who used to export a CSV every Monday morning. Once it’s built, your revenue, top products, and repeat-customer patterns are always current, and you can hand that sheet to anyone on your team without giving them store access.
Recover Money You’re Already Losing
3. Abandoned Cart → A WhatsApp Nudge, Not Another Buried Email
The trigger: cart abandoned. The action: a WhatsApp message, sent to the phone number the customer already gave you at checkout.
A lot of cart-recovery emails end up buried in a promotions tab, opened by nobody. A WhatsApp message from a real-feeling business number tends to land somewhere the customer actually checks. One requirement worth knowing before building this: WhatsApp only allows business messages to numbers that have opted in, so this runs off the number a customer gives you at checkout, not a list you already have sitting somewhere else. This is worth its own deep dive since the setup has a few extra steps, but the short version is: connect WooCommerce, connect WhatsApp, and trigger the message on the same abandoned-cart event you’re probably already using for email.
4. A Consumable Running Low, for the Customer, Not the Warehouse
The trigger: enough time has passed since a specific product’s typical repurchase window that a customer is likely running low. The action: an automatic “time to reorder” message, timed to that product, not a flat number of days used for every SKU.
Most automation guides cover the store’s stock running low. This flips it. A store rarely runs out of everything at once, but individual customers run out of specific things on a schedule of their own, coffee, supplements, skincare, anything consumable. If you can see how long it typically takes between a customer’s first and second order of the same product, you can send the reminder right before they’d have gone looking for it anyway, instead of a generic “haven’t seen you in a while” email that lands either too early to matter or too late to catch the reorder.
5. Subscription or Renewal Failure → A Recovery Sequence, Not a Lost Customer
The trigger: a failed subscription renewal or a payment that didn’t go through. The action: an automated follow-up sequence, starting with a simple “your payment didn’t go through” message and escalating if there’s no response.
Failed payments are usually boring and fixable, an expired card, a bank flagging the charge, nothing to do with whether the customer still wants your product. Catching this automatically, instead of finding out a month later when nobody’s paid, is one of the most valuable automations on this list for any store with recurring revenue.
Turn One Sale Into the Next One
6. Delivery Confirmed → A Review Request That Actually Confirms It Worked
The trigger: order status changed to completed or delivered. The action: an email or WhatsApp message asking for a review, a day or two after delivery.
The part most setups miss by default: they send this message once, on a timer, and stop there. A newer capability changes that, the same workflow can wait for a reply through a webhook, so if a customer clicks through and leaves a review, that response can trigger something back, a thank-you, a discount code for next time, instead of firing once and going quiet. Ask for a review the same day the order ships and you’ll get silence, the product hasn’t arrived yet. Build in the two-way step and the request stops being a one-shot guess.
7. New Customer → Booked in for Onboarding, Automatically
The trigger: a first-time purchase. The action: a booking link sent automatically, inviting the customer to a short onboarding or “getting started” call.
This one’s newer and most stores haven’t thought to build it yet: connect your booking tool the same way you’d connect Slack or Sheets, and a first-time customer gets invited to a real conversation without anyone on your team remembering to send the invite. For anything with a learning curve (courses, software, higher-ticket physical products), this turns a one-time sale into a relationship before the customer’s even used what they bought.
What Happens When One of These Breaks
Any automation can fail, an API changes, a webhook times out, a workflow hits its monthly task limit. The real question isn’t whether that ever happens, it’s whether you find out that day or three weeks later when a customer asks why they never got a shipping confirmation. OttoKit logs every run and can alert you the moment one fails, by email, WhatsApp, or push, and a failed run can be replayed with one click instead of rebuilt from scratch. Worth confirming any tool you use for this does the same before you’re relying on seven of them at once.
Where to Start if You Only Build One This Week
Start with #1. It takes minutes, needs no design decisions, and it’s exactly the kind of automation that turns a connected integration into something you’ve actually built and used, which is where most people currently stop. Once it’s live and you’ve felt the difference, the rest get easier to justify, because you’ve seen automation work instead of reading about it working.
Frequently Asked Questions
Do I need to know how to code to set these up?
No. Every workflow above is built by picking a trigger, picking an action, and connecting the two, the same way you’d set up a rule in an email inbox.
Will this work with my existing WooCommerce plugins?
Automations trigger WooCommerce’s own order and product events, so they sit alongside whatever extensions or page builder you’re already running rather than replacing anything.
What if I only want one or two of these, not all seven?
Build one, let it run for a week, then add the next. There’s no requirement to set all seven up at once, and doing them one at a time is exactly how most stores actually succeed with automation instead of stalling out.
Do I need a paid plan to build these?
No. OttoKit’s free plan includes 250 tasks a month, plenty for a small store to run several of these without paying. If your order volume is high enough that alerts, sheet updates, and follow-ups add up fast, paid plans start at $9/month (billed annually) for 5,000 tasks and scale up from there.
