How to Automate Shopify Order Status Lookups With n8n

A Shopify order status lookup automation in n8n turns the endless stream of where-is-my-order emails into instant, hands-off replies. A customer submits their order number and email on a simple form, n8n queries the Shopify Admin API, and within seconds they receive a message with the exact fulfillment status and live tracking link. No support agent, no copy-pasting tracking numbers, and your inbox is freed for real problems.

Prefer to skip the setup? Grab the ready-made template → and be answering order status requests automatically in under 10 minutes.

What it does

Where-is-my-order requests, often shortened to WISMO, are the single most common message a Shopify store receives. Industry surveys put them at 40 to 60 percent of all support tickets, and every one of them has the same answer already sitting in your Shopify admin. Answering them by hand is pure repetition: open the order, read the fulfillment status, copy the tracking link, paste it into a reply.

This workflow removes that loop entirely. It is a reactive lookup, which makes it different from a shipping confirmation email that fires once when an order ships. Here the customer asks at any moment, and the automation answers on demand with whatever the current status is. It sits neatly alongside your other Shopify n8n automations as the front line of self-service support.

┌──────────────────────────────────────────────────────────────┐
│  SHOPIFY ORDER STATUS LOOKUP (WISMO AUTO-REPLY)               │
│                                                              │
│  [Lookup Form]                                               │
│       │  order # + email                                     │
│       ▼                                                      │
│  [Webhook] → [Shopify Admin API lookup] → [Order found?]     │
│                                              │        │       │
│                                     yes ◄────┘        └──► no │
│                                      ▼                    ▼   │
│                          [Build status reply]     [Email:    │
│                                      ▼             not found] │
│                          [Email customer status]             │
│                                      ▼                        │
│                          [Telegram ping to merchant]         │
└──────────────────────────────────────────────────────────────┘
  

Why it beats the default

The default Shopify experience does give buyers an order status page and shipping emails. So why do they still email you? Because they lost the email, the link expired from their point of view, or they simply want a human to confirm. The out-of-the-box tools are passive; they wait to be found. This workflow is active: the moment a customer reaches out, they get a personal reply with the live answer.

Compared to a paid help-desk app with a WISMO add-on, the n8n version costs nothing per ticket and stays entirely under your control. You decide the wording, the branding, and which channel the reply goes out on. And because it reads directly from the Shopify Admin API at request time, the status is never stale, unlike a cached export or a nightly sync.

What you need

• A Shopify store with Admin API access. If you have not connected Shopify to n8n yet, follow the 2026 Shopify to n8n connection guide first, it uses the current Dev Dashboard method to create your access token.
• An n8n instance (cloud or self-hosted), version 1.0 or later.
• A Gmail account (or Outlook / SMTP) to send the reply from.
• A Telegram bot and chat ID for the optional merchant ping. This is a nice-to-have, not required.
• A simple lookup form on your store that POSTs the order number and email to the n8n webhook. A plain HTML form or any form app that can send a webhook works.

Estimated build time: 30 to 45 minutes from scratch, or under 10 minutes with the template.

Node-by-node list

Seven nodes, one clean branch. Here is the full map before we build it:

Step-by-step build

1 Where Is My Order? (Webhook)

This node is the entry point. It gives you a URL that your lookup form posts to.

1. Add a Webhook node and set the HTTP Method to POST.
2. Set a path such as order-status.
3. Set Respond to Immediately so the form gets a fast acknowledgement while the rest of the flow runs.
4. Point your store form at the production webhook URL, sending two fields: order_number and email.

After a submission, the data arriving looks like this:

{
  "order_number": "1042",
  "email": "james.carter@gmail.com"
}

2 Look Up Order (HTTP Request)

This node calls the Shopify Admin API and asks for the order by its name.

1. Add an HTTP Request node, Method GET.
2. Set the URL to your store’s orders endpoint on API version 2026-04:
   
   https://YOUR_STORE.myshopify.com/admin/api/2026-04/orders.json
3. Turn on Send Query Parameters and add:
   • name = ={{ $json.order_number }}
   • status = any
   • fields = name,email,financial_status,fulfillment_status,fulfillments,customer
4. Under Authentication, choose Generic Credential Type → Header Auth and set the header name to X-Shopify-Access-Token with your Admin API token as the value.

Shopify returns an orders array. A matched order carries everything you need:

{
  "orders": [
    {
      "name": "#1042",
      "email": "james.carter@gmail.com",
      "financial_status": "paid",
      "fulfillment_status": "fulfilled",
      "fulfillments": [
        { "tracking_number": "9400111899223197428490",
          "tracking_url": "https://tools.usps.com/go/TrackConfirmAction?tLabels=9400111899223197428490" }
      ],
      "customer": { "first_name": "James" }
    }
  ]
}

3 Order Found? (IF)

This node splits the flow depending on whether Shopify returned a match.

1. Add an IF node.
2. Create one condition. Left value: ={{ $json.orders.length }}, type Number.
3. Operation: is greater than. Right value: 0.

The true output goes to Build Status Reply. The false output goes to Email Not Found.

4 Build Status Reply (Edit Fields)

This node pulls the raw Shopify response into a handful of clean, named fields your email can reference.

1. Add an Edit Fields (Set) node on the true branch.
2. Add these string assignments:
   • first_name = ={{ $json.orders[0].customer.first_name }}
   • order_name = ={{ $json.orders[0].name }}
   • status = ={{ $json.orders[0].fulfillment_status || "unfulfilled" }}
   • tracking_url = ={{ $json.orders[0].fulfillments[0]?.tracking_url || "" }}

The result is a tidy object that is easy to drop into an email template:

{
  "first_name": "James",
  "order_name": "#1042",
  "status": "fulfilled",
  "tracking_url": "https://tools.usps.com/go/TrackConfirmAction?tLabels=9400111899223197428490"
}

5 Email Order Status (Gmail)

This node sends the customer their answer.

1. Add a Gmail node, operation Send.
2. To: ={{ $('Where Is My Order?').item.json.email }}
3. Subject: Your order {{ $json.order_name }} status
4. Message body, for example:

Hi {{ $json.first_name }},

Here is the latest on order {{ $json.order_name }}:

Status: {{ $json.status }}
Tracking: {{ $json.tracking_url }}

Thanks for shopping with us!

6 Ping Merchant (Telegram, optional)

A quiet log so you can see the automation working.

1. Add a Telegram node, operation Send Message.
2. Chat ID: your YOUR_TELEGRAM_CHAT_ID.
3. Text: WISMO answered for {{ $json.order_name }} ({{ $json.status }}).

7 Email Not Found (Gmail)

On the false branch, reassure the customer rather than leaving them with silence.

1. Add a second Gmail node, operation Send.
2. To: ={{ $('Where Is My Order?').item.json.email }}
3. Body: tell them you could not match that order number and a team member will follow up, and ask them to double-check the number from their confirmation email.

Common mistakes

Cost at realistic volume

The appeal of this build is that it runs on tools you already pay for, or free tiers. Assume a store fielding 600 WISMO requests a month, a busy small brand.

Against a help-desk app that charges per resolved ticket, answering 600 requests automatically each month is the difference between a recurring bill and effectively zero. The time saved is the bigger prize: at two minutes of manual handling per ticket, 600 lookups is 20 hours a month you get back.

FAQ

Related guides

• Shopify shipping confirmation email with tracking in n8n
• Build a Shopify AI customer support chatbot with n8n
• Send Shopify alerts to Telegram with n8n
• Browse every store automation in the Shopify category.