Shopify order cancellation automation with n8n

A Shopify order cancellation automation in n8n turns a cancelled order into three things that otherwise sit on somebody’s to-do list: a clear email to the customer, a row in a Google Sheets log you can actually audit, and an alert to your ops address when the order shipped before it was cancelled so inventory will not come back on its own. Six nodes, one webhook, no polling. Here is the whole build.

What it does

The workflow listens to the Shopify orders/cancelled webhook. The moment an order is cancelled, whether from the admin, the API, or an app, Shopify pushes the full order payload to n8n and the workflow does three things in parallel.

1. Emails the customer a plain confirmation naming the order, the items removed, the amount refunded so far, and the reason on record.
2. Appends one row to a Cancellations sheet with eleven columns, so you can count cancellations by reason and by month without exporting anything.
3. Checks whether the order was already fulfilled or partially fulfilled at the moment of cancellation. If it was, Shopify will not put that stock back, so the workflow emails your ops address with the exact line items to check.

┌──────────────────────────────────────────────────────────────┐
│  SHOPIFY ORDER CANCELLATION AUTOMATION                       │
│                                                              │
│  [Order Cancelled] → [Build Cancellation Data]               │
│                             │                                │
│              ┌──────────────┼──────────────┐                 │
│              ↓              ↓              ↓                 │
│   [Email Customer]  [Log To Sheets]  [Needs Restock?]        │
│                                             │ true           │
│                                             ↓                │
│                                    [Alert Ops To Restock]    │
└──────────────────────────────────────────────────────────────┘

Why it beats the default

Shopify’s built-in cancellation email is a receipt. It confirms the cancellation and stops there. Three gaps stay open.

The first is the restock gap. When you cancel an order in the Shopify admin you get a restock checkbox, and it only covers items that were never fulfilled. Cancel an order that already shipped and those units stay deducted from your inventory even though the goods may be on their way back to you. Nothing in Shopify tells you this happened. Two weeks later a product shows as out of stock while three units sit in a returns bin. This workflow catches that case on the spot and names the line items.

The second gap is the reason log. Shopify stores cancel_reason on the order, but there is no report that groups cancellations by reason over time. Once every cancellation lands in a sheet, “customer changed mind” versus “inventory” versus “fraud” becomes a number you can act on rather than a hunch.

The third gap is refund clarity. The default email does not tell a customer how much has actually been refunded or when it will land. That single missing sentence is what generates the follow-up support ticket. Saying “refunded so far, typically 5 to 10 business days” up front removes most of them.

What you need

• An n8n instance, cloud or self-hosted, version 1.0 or newer.
• A Shopify credential in n8n. Use the 2026 Dev Dashboard method described in how to connect Shopify to n8n in 2026. The old admin custom-app flow has been removed, so follow the current path. The trigger needs the read_orders scope.
• A Gmail credential, used for both the customer email and the ops alert. A Google Workspace address on your own domain sends better than a free Gmail address.
• A Google Sheets credential and one spreadsheet with a tab named Cancellations.
• An internal address to receive restock alerts, for example ops@yourstore.com.

The Cancellations sheet

Create the tab and put these exact headers in row 1. The Google Sheets node maps by column name, so a typo here is the single most common reason rows land blank.

Node-by-node list

Step-by-step build

1. Create a new workflow and name it Shopify Order Cancellation Automation.
2. Add a Shopify Trigger node, rename it to Order Cancelled, set Authentication to Access Token, attach your Shopify credential, and set Topic to orders/cancelled. n8n registers the webhook with Shopify when you activate the workflow, so there is nothing to configure on the Shopify side.
3. Add an Edit Fields node named Build Cancellation Data. Leave Mode on Manual Mapping and add twelve assignments. The straightforward ones map directly: order_number to {{ $json.order_number }}, order_id to {{ $json.id }}, customer_email to {{ $json.email }}, cancelled_at, currency, and order_total to {{ $json.total_price }}.
4. Add customer_name as a string with a fallback, because guest checkouts can arrive with no customer object attached:

   {{ $json.customer && $json.customer.first_name ? $json.customer.first_name : 'there' }}

5. Add cancel_reason as {{ $json.cancel_reason || 'unspecified' }}. Shopify leaves this null when an order is cancelled through the API without a reason, and a null in the email body reads badly.
6. Add items_list, which flattens the line items into one readable string used by both emails and the sheet:

   {{ ($json.line_items || []).map(i => i.quantity + ' x ' + i.title).join(', ') }}

7. Add refund_total. Refunds live in a nested array of transactions, so sum them and fix to two decimals:

   {{ ($json.refunds || []).reduce((sum, r) => sum + (r.transactions || []).reduce((t, x) => t + parseFloat(x.amount || 0), 0), 0).toFixed(2) }}

8. Add fulfillment_status as {{ $json.fulfillment_status || 'unfulfilled' }}. Shopify sends null rather than the string “unfulfilled” when nothing has shipped, which would otherwise break the next expression.
9. Add needs_manual_restock and set its type to Boolean, not string. This is the flag the IF node reads:

   {{ ['fulfilled', 'partial'].includes($json.fulfillment_status) }}

10. Add a Gmail node named Email Customer Confirmation. Set To to {{ $json.customer_email }}, Subject to Your order #{{ $json.order_number }} has been cancelled, and Email Type to HTML. Write the body naming the items, the refunded amount, and the 5 to 10 business day window. Under Options, turn off Append n8n attribution.
11. Add a Google Sheets node named Log Cancellation To Sheets. Operation is Append Row in Sheet. Pick your spreadsheet, choose the Cancellations tab, set Mapping Column Mode to Map Each Column Manually, and fill the eleven columns from the table above.
12. Add an IF node named Needs Manual Restock?. Left value {{ $json.needs_manual_restock }}, condition type Boolean, operator is true. Leave the right value empty since is true is a single-value operator.
13. Add a second Gmail node on the true branch named Alert Ops To Restock. Send it to your ops address with subject Manual restock needed: order #{{ $json.order_number }} and a body naming items_list, the fulfillment status, and the refunded amount. Leave the false branch unconnected.
14. Wire Build Cancellation Data to all three of the customer email, the Sheets node, and the IF node from its single output. n8n runs the three branches in sequence but each receives the same item, so a Gmail hiccup does not block the sheet row.
15. Save, then toggle Active. Activation is what registers the webhook with Shopify.

Common mistakes

Storing the restock flag as a string

If needs_manual_restock is typed as a string, the value arrives as "true" and an IF node running strict type validation refuses to compare it to a boolean. Set the field type to Boolean in the Edit Fields node and the comparison works. This is the single most common failure in this build.

Assuming fulfillment_status is always a string

For an order where nothing shipped, Shopify sends "fulfillment_status": null. Call .includes() on that without the || 'unfulfilled' fallback and the node throws on roughly nine out of ten cancellations, since most cancellations happen before shipping.

Sheet headers that do not match exactly

Order number is not Order Number. The Google Sheets node matches on the exact header string, and a mismatch produces a row with blank cells rather than an error, so it fails quietly for weeks. Copy the headers from the table above.

Expecting a refund amount on every cancellation

Cancelling and refunding are separate operations. An order cancelled without a refund fires the webhook with an empty refunds array, so refund_total is 0.00. The email wording of “refunded so far” keeps that accurate instead of promising money that is not moving.

Deactivating and reactivating repeatedly

Each activation registers a fresh webhook subscription with Shopify. Toggling the workflow on and off many times while testing can leave orphaned subscriptions that deliver duplicate payloads. If you start seeing double emails, list your webhooks through the Admin API and delete the stale ones.

Cost at realistic volume

This workflow is webhook-driven, so it consumes nothing at all on days with no cancellations. That matters because cancellations are rare compared to orders.

Gmail’s free sending limits are 500 messages a day for a personal account and 2,000 for Workspace, so even the busiest case here uses a fraction of one day’s quota. Google Sheets API quotas are far above this. The realistic cost is your n8n hosting, which you are already paying for if you run any other n8n Shopify automation.

FAQ

Related guides

• How to connect Shopify to n8n in 2026, the Dev Dashboard credential setup this workflow assumes.
• Shopify refund tracker in Google Sheets, which covers the refund side that cancellation only partly overlaps.
• Shopify returns automation with n8n, for goods coming back after delivery rather than orders stopped mid-flight.
• Shopify failed payment recovery email, the other common reason an order never completes.
• The full n8n Shopify automation hub and every post in the Shopify category.