Shopify webhooks in n8n explained (with a live order alert)

Shopify webhooks in n8n explained, without the jargon: a webhook is a message your store fires to a URL the instant something happens, like a new order landing or a product selling out. Instead of your automation nagging Shopify every few minutes to ask what changed, Shopify pushes the event to you the moment it occurs. This guide shows what webhooks are, why they beat scheduled polling for a Shopify store, and how to build a validated three node workflow that pings your phone on Telegram the second an order comes in.

What it does

The demo workflow watches a single Shopify event, the orders/create topic, and turns every new order into an instant Telegram message. When a customer checks out, Shopify delivers the full order payload to n8n, a Set node formats it into a short human readable summary, and a Telegram node sends it to your chat. You get a ping like this within a second of the sale:

🛒 New order #1042
Customer: Emily Rodriguez
Total: 128.40 USD
Items: 3
  

No dashboard refreshing, no email digest that arrives an hour late. The order alert reaches you while the customer is still on the thank you page. Once you understand this pattern, the same webhook plumbing drives every other real time Shopify automation you will ever build in n8n.

Why it beats the default

The common alternative is polling: a Schedule trigger that asks Shopify for recent orders every few minutes. Polling works, but it has three real costs. It is slow, because your alert is only as fresh as the interval, so a five minute schedule means a five minute delay. It is wasteful, because most of those requests return nothing new yet still count against your Shopify API rate limit. And it is fragile, because you have to track which orders you already saw to avoid sending duplicate alerts.

A webhook flips all three. Shopify only contacts you when the event genuinely happens, so the alert is near instant, you spend zero API calls waiting for nothing, and every delivery is a distinct event so there is no de-duplication logic to maintain. For anything that should feel live, a webhook is the correct tool.

What you need

• An n8n instance, either n8n Cloud or self hosted, version 1.0 or newer.
• A Shopify store where you can create a custom app for API access. Follow our 2026 guide to connecting Shopify to n8n first, since the Shopify Trigger needs an access token credential.
• A Telegram account and a bot token from BotFather, plus your numeric chat ID for the destination.
• About 15 minutes to build from scratch, or 2 minutes with the ready made template.

Node-by-node list

Three nodes, one straight line. Here is what each one is and why it exists.

• Shopify order webhook — a Shopify Trigger node set to the orders/create topic. This is the webhook. It registers the subscription with Shopify and fires once per new order, handing the full order object to the next node.
• Build alert message — a Set (Edit Fields) node that reads the order fields and composes one tidy string. This keeps the message logic separate from the sending, so you can restyle the alert without touching Telegram.
• Send Telegram alert — a Telegram node that posts the composed message to your chat. Swap it for a Gmail node later if you prefer email; the first two nodes stay identical.

┌──────────────────────────────────────────────────────────────┐
│  SHOPIFY WEBHOOK → TELEGRAM ORDER ALERT                        │
│                                                                │
│  [Shopify order webhook] → [Build alert message] → [Telegram]  │
│    orders/create             Set / Edit Fields       send      │
└──────────────────────────────────────────────────────────────┘
  

Step-by-step build

1. Create a new workflow in n8n and add a Shopify Trigger node. In its settings, set Authentication to Access Token and pick the Shopify credential you created in the connection guide.
2. In the same node, set the Topic to orders/create. That single choice tells Shopify to notify n8n every time an order is placed. Leave everything else at its default.
3. Add a Set node (also called Edit Fields) and connect the trigger to it. Add one assignment named message of type String.
4. Paste this expression as the value of message, using the expression editor so the {{ }} parts resolve against the order:

   🛒 New order {{ $json.name }}
   Customer: {{ $json.customer.first_name }} {{ $json.customer.last_name }}
   Total: {{ $json.total_price }} {{ $json.currency }}
   Items: {{ $json.line_items.length }}

5. Add a Telegram node and connect the Set node to it. Choose your Telegram credential, set Resource to Message and Operation to Send Message.
6. In the Telegram node, set Chat ID to your numeric chat ID, and set Text to the expression {{ $json.message }} so it sends the string the Set node built.
7. Click Save, then toggle the workflow Active. Activating it is what registers the real webhook with Shopify. Place a test order, or use Shopify’s webhook test button, and watch the alert arrive in Telegram.

Common mistakes

• Building the whole thing but never toggling the workflow Active. In test mode the webhook is temporary, so live orders never reach it. The permanent subscription exists only while the workflow is on.
• Referencing a customer field on a guest checkout that has none. If some orders come in without a customer object, guard the expression, for example {{ $json.customer?.first_name || "Guest" }}, so the Set node never errors.
• Using the wrong topic. orders/create fires on new orders; orders/paid fires only after payment clears. Pick the one that matches the moment you actually care about.
• Expecting duplicate protection from n8n. Webhooks are one event per delivery, so if you also keep an old polling workflow running you will get two alerts. Retire the poller once the webhook works.

Cost at realistic volume

This workflow is close to free at any small store volume. Shopify does not charge for webhook deliveries. Telegram bot messages are free. On n8n Cloud, each order alert is a single execution, so a store doing 40 orders a day uses about 1,200 executions a month, which sits inside the entry paid tier. Self hosted n8n has no per execution cost at all.

The only line item to watch is your n8n Cloud plan’s execution allowance. If order volume climbs into the thousands per day, self hosting removes that ceiling entirely.

Frequently asked questions

Related guides

• How to connect Shopify to n8n in 2026 — the credential setup this workflow depends on.
• Shopify alerts on Telegram with n8n — more real time notifications built on the same trigger.
• The complete guide to n8n Shopify automation — every store workflow in one hub.
• Browse all Shopify automation guides.
• The n8n template library
• Best n8n AI agent templates for Shopify