Shopify Automation Workflows in n8n: 7 to Build First

The Shopify automation workflows worth building first in n8n are the ones you repeat every day with the same inputs: copying orders into a packing sheet, checking overnight orders and refunds, catching low stock, and answering "where is my order" emails. For a store under 500 orders a month, the seven n8n workflows below save an estimated 8.5 hours a week, ranked by hours. Each one lists its trigger and the exact nodes to drag in, so you can build it this week or hand the list to whoever runs your store.

Assumptions behind the hours

Every hour figure here is an estimate for one example store, not a measured result. Change the inputs and the ranking can change too.

• 400 orders a month, which is 400 × 12 ÷ 52 = about 92 orders a week.
• One in five orders produces a customer email about order status: about 18 a week.
• About 4 refunds a week.
• Someone checks the store each weekday morning by hand today.

The manual work is real at stores much bigger than this one. Shopify's own guide to order management cites a survey finding that "52% of fulfillment operations are still mostly manual." Small stores are no exception.

The 7 workflows, ranked by hours saved

The total is 138 + 100 + 75 + 72 + 50 + 46 + 32 = 513 minutes, or about 8.5 hours a week. All three webhook topics in the table appear in Shopify's webhooks reference, so you are not relying on a third-party connector to fire them.

Workflow nodes, one by one

n8n's Shopify node covers two resources, Order and Product, with create, delete, get, get all and update operations. Anything else (inventory by location, fulfillment details) goes through an HTTP Request node against the Shopify Admin API. Keep that in mind when a step below says "HTTP Request."

1. Order export to packing sheet (2.3 hours). Shopify Trigger (orders/create) → Code (flatten line items into one row per SKU) → Google Sheets (append row) → IF (order contains a preorder or wholesale SKU) → Slack (post to #fulfillment). The IF branch is the part people skip, and it is the part that stops a preorder from shipping early.

2. Morning ops summary (1.7 hours). Schedule Trigger (weekdays 7:00) → Shopify (Order: Get All, created since yesterday 7:00) → Aggregate (count orders, refunds, unfulfilled) → AI Agent node with an LLM (write five plain lines: totals, anything unusual, anything waiting on a person) → Slack or Gmail. One screen people read every morning beats five dashboards nobody opens.

3. Low-stock alert with reorder draft (1.25 hours). Schedule Trigger (daily) → Shopify (Product: Get All) → Code (keep variants under your reorder point) → IF (any rows) → Gmail (create draft to the supplier, with SKU, quantity on hand and suggested order). The draft step matters. A person approves the purchase; the workflow only does the typing.

4. Order-status email drafts (1.2 hours). Gmail Trigger (new email in the support inbox) → AI Agent with an LLM (classify: order status, return, other) → IF (order status) → Shopify (Order: Get All, filtered by order number or email) → AI Agent (draft a reply using the tracking data) → Gmail (create draft, never send). The 4 minutes saved per email comes from not opening Shopify and the carrier site. Our where-is-my-order playbook covers the reply templates in detail.

5. Stuck-order watchdog (0.8 hours). Schedule Trigger (daily) → Shopify (Order: Get All, open and unfulfilled) → Filter (created more than 48 hours ago) → Slack (list with order links). This is the workflow that catches problems before the customer emails about them.

6. Post-delivery review request (0.8 hours). Shopify Trigger (orders/fulfilled) → IF (customer accepted email) → Wait (7 days, or your typical delivery time plus a few days) → Gmail (send the request). Ask every customer who agreed to email, not only the ones you expect to be happy: filtering for happy customers first is review gating, which many review platforms do not allow.

7. Refund log for bookkeeping (0.5 hours). Shopify Trigger (refunds/create) → Code (pull order number, amount, reason, date) → Google Sheets (append to the refunds tab your bookkeeper reads). Small, but it removes a monthly hunt through the admin.

What this costs to run on n8n

n8n prices by executions. Its pricing page says "Pricing based on monthly workflow executions, regardless of complexity," and for webhook workflows it advises: "Estimate how many times the event that triggers your webhook occurs per day. That number equals your daily executions." Applying that to the example store:

The same page lists the Starter cloud plan at "20€ /mo, billed annually" with "2.5K workflow executions with unlimited steps," so the whole set fits with room to spare. n8n also offers a self-hosted Community Edition. LLM usage for workflows 2 and 4 is billed separately by whichever model provider you connect.

When Shopify Flow is enough, and when to do it by hand

Shopify's help center says "Shopify Flow is a free app available on the Basic, Grow, Advanced, and Plus plans." If a rule starts and ends inside Shopify (tag a high-value order, hide a sold-out product, flag a risky order), build it in Flow and skip n8n entirely. Use n8n when a step leaves Shopify: a Google Sheet, a supplier email, a Slack channel, an AI draft.

Some work should stay manual:

• Anything that happens less than twice a month. A quarterly wholesale reorder is faster to do by hand than to build.
• Replies to angry or unusual customers. Workflow 4 drafts the routine ones and leaves the rest alone.
• Refund decisions. Workflow 7 logs refunds; a person still approves them.

Where these workflows break first

Most n8n failures on a small store are boring, and they cluster in the same few places.

Duplicate events. Treat every webhook as something that might arrive twice. In workflow 1, look up the order ID in the sheet before appending a row; in workflow 6, record that a review request went out so a retry cannot send a second one. A Google Sheets lookup or a small Code node check is enough.

Time zones. A Schedule Trigger runs in the n8n instance's time zone, and Shopify timestamps carry their own offset. If the morning summary says "yesterday," make sure both sides agree on when yesterday started, or orders placed late in the evening go missing from the count.

Edited orders. Customers change addresses and staff add items after orders/create has already fired. If your packing sheet must match the final order, add a second workflow on orders/updated that rewrites the row, or have the packer check Shopify for any order flagged as edited.

Paging. "Get All" in the Shopify node needs the Return All option, or a filter by date, or the low-stock check quietly stops at the first page of products. Test it with a store that has more products than one page holds.

Expired credentials. When someone removes the custom app or rotates a token, every workflow fails at once. The error workflow from the checklist below is what turns a silent outage into a Slack message.

Build checklist before you turn anything on

• Create a separate Shopify custom app for n8n with only the scopes each workflow needs (orders read, products read).
• Turn on n8n's error workflow so a failed run posts to Slack or email.
• Run every webhook workflow against test orders first, then watch real orders for a week.
• Keep anything customer-facing on "create draft" for the first two weeks.
• Write one line per workflow in a shared doc: what it does, its trigger, who to tell if it breaks.
• Recheck the hour estimates after a month and reorder the list if your store differs.

That last step is where the real ranking comes from. On the Shopify store we run day to day for a kids wellness brand (orders, refunds, fulfillment for a network of schools and the quarterly sales-tax numbers, per the Yogapalooza case study), the order of automations came from doing the work by hand first and timing it, not from a generic list.

Build it yourself or hand it off

If you are comfortable in n8n, the seven workflows above are a few weekends of work, and you will learn your store better by building them. Before you add another paid app for any of these jobs, run the numbers in our app subscription vs custom automation breakdown. More guides like this sit in the playbooks hub and the Shopify brands hub.

If you would rather not, our Shopify ops and AI automation retainer runs the store work and ships one of these workflows a month, built in your own n8n and Shopify accounts. Not sure which of the seven costs you the most hours? Start with a free ops audit: tell us where your week goes and we send back the three jobs we would automate first, with the hours each one saves.