Ecommerce automation with n8n lets you wire your store to the tools you already use, such as Google Sheets, Telegram, Gmail, and your CRM, without paying for a stack of single-purpose apps. This guide maps the workflows worth building first, explains why n8n beats the default app-per-task approach, and walks you through a working starter automation that logs every new order to a spreadsheet and pings you on Telegram the moment it lands.
What ecommerce automation with n8n actually covers
n8n is an open-source automation tool. You build workflows on a visual canvas by connecting nodes: something triggers the flow (a new order, a schedule, a low-stock event), the data gets shaped, and one or more actions fire (a row appended, an email sent, a channel pinged). For an online store, that maps onto a handful of jobs you run over and over. Here are the ones most stores automate first, each with a full how-to if you want to go deep on that one.
Orders and fulfillment
- Log every new order to Google Sheets for a running sales ledger your accountant can actually open.
- Get order alerts on Telegram so you see revenue land in real time without refreshing the admin.
- Auto-tag orders by value, location, or product so fulfillment can filter at a glance.
- Send branded shipping confirmations with tracking, on your terms instead of the default template.
Inventory and catalog
- Low-stock alerts before you sell something you cannot ship.
- Auto-email suppliers a reorder when a SKU drops below its threshold.
- Generate product descriptions with AI from a title and a few bullet points.
Customers and retention
- Recover abandoned checkouts with a timed email sequence.
- Follow up after purchase to ask for a review or cross-sell.
- Win back lapsed buyers automatically once they go quiet.
- Segment customers by RFM so your best buyers get your best offers.
- Answer support questions with an AI chatbot trained on your own store data.
That is the roundup. If you run Shopify specifically, the n8n Shopify automation hub is the deeper index of every Shopify build on this site. This page is the broader ecommerce view, and every workflow above works just as well on WooCommerce through its own node. New to connecting a store at all? Start with connecting Shopify to n8n, or the WooCommerce setup guide.
Why it beats the default
The default path is one app per task. An app for order alerts, another for spreadsheet exports, another for review requests, each with its own monthly fee and its own dashboard. Three or four of those and you are paying more every month than a whole automation platform costs, with data scattered across tools that do not talk to each other.
n8n flips that. One instance owns all of it, and the workflows share data. The same order that gets logged to a sheet can trigger the low-stock check and the customer tag in the same run. A few concrete advantages:
- Flat cost. Self-hosted n8n runs unlimited executions on a 5-dollar VPS. You are not billed per task or per contact.
- No platform lock-in. The Shopify node and the WooCommerce node live in the same tool, so switching or running both stores is a node swap, not a rebuild.
- You own the logic. Export any workflow as JSON, back it up, share it, or move it to another server. Nothing is trapped behind a vendor account.
- Composable. Every workflow can call the next. That is impossible when each task lives in a separate closed app.
What you need
To build the starter workflow below (a new order that logs to a sheet and alerts you on Telegram) you need four things:
- An n8n instance, cloud or self-hosted. The workflow imports the same on either.
- A Shopify store connected to n8n with an Admin API access token. Follow the 2026 connection guide first if you have not done this. (On WooCommerce, swap the trigger for the WooCommerce Trigger node; the rest is identical.)
- A Google account with a blank spreadsheet to receive the order rows.
- A Telegram bot token and your chat ID for the alert. Message @BotFather to create a bot, and @userinfobot to read your chat ID.
Build time: about 20 minutes from scratch, or under 5 minutes if you import the ready-made template below.
Node-by-node list
The starter is four nodes. Data flows from the trigger, gets shaped once, then fans out to both actions in parallel.
New Shopify Order --> Build Order Summary --> Log to Google Sheets
(trigger) (Set fields)
--> Send Telegram Alert
| # | Node | Type | Job |
|---|---|---|---|
| 1 | New Shopify Order | shopifyTrigger |
Fires on orders/create and hands over the raw order. |
| 2 | Build Order Summary | set (Edit Fields) |
Pulls five clean fields out of the order payload. |
| 3 | Log to Google Sheets | googleSheets |
Appends one row to your Orders sheet. |
| 4 | Send Telegram Alert | telegram |
Sends the summary to your chat. |
Step-by-step build
- Add the trigger. Drop in a Shopify Trigger node, set Authentication to Access Token, attach your Shopify credential, and set the topic to
orders/create. n8n registers the webhook with Shopify for you. - Shape the data. Add an Edit Fields (Set) node. Create five string fields so the rest of the flow works with clean values instead of the deep order object:
order_number = {{ $json.order_number }} customer_name = {{ $json.customer.first_name }} {{ $json.customer.last_name }} total = {{ $json.total_price }} currency = {{ $json.currency }} placed_at = {{ $json.created_at }} - Log to the sheet. Add a Google Sheets node, operation Append Row. Pick your spreadsheet and the
Orderstab, then map the columns to the five fields above (Order, Customer, Total, Currency, Placed at). - Send the alert. Add a Telegram node, operation Send Message. Paste your chat ID and set the text to an expression:
New order {{ $json.order_number }} Customer: {{ $json.customer_name }} Total: {{ $json.total }} {{ $json.currency }} - Fan out in parallel. Wire the Set node to both the Google Sheets node and the Telegram node. One output can feed two nodes, so a single order is logged and alerted in the same run.
- Save and activate. Save the workflow, toggle it Active, and place a test order (or use a Shopify test payment). A row appears in your sheet and a message hits Telegram within seconds.
Tip: Keep the Set node even for tiny flows. Shaping the order once, up front, means every downstream node reads the same five fields. When you add a third action later (an email, a CRM push), it just reuses them.
Common mistakes
- Referencing the raw order everywhere. Without the Set node, each action digs into
$json.customer.first_nameand friends on its own. One payload change and you fix it in five places. Shape once, reference the clean field. - Chaining actions instead of fanning out. If you wire Sheets, then Telegram after it, a Sheets error blocks the alert. Branch both off the Set node so they run independently.
- Wrong Shopify auth. The removed legacy custom-app flow no longer applies. Use an Admin API access token via the 2026 Dev Dashboard method, or the trigger throws a 401.
- Header row mismatch. The Google Sheets append maps by column name. If your sheet header says
Order #but the mapping saysOrder, the value lands in the wrong place or a new column. - Testing with the workflow inactive. The Shopify Trigger only receives live webhooks when the workflow is Active. In the editor, use Execute Node with a sample, but confirm end to end with the workflow switched on.
Cost at realistic volume
Say you take 1,000 orders a month. Every order runs this workflow once, so that is 1,000 executions. Here is what that actually costs across the pieces:
| Component | Cost at 1,000 orders/month |
|---|---|
| n8n (self-hosted on a small VPS) | ~$5/month, unlimited executions |
| n8n Cloud (if you prefer managed) | From ~$20/month, well within starter execution limits |
| Google Sheets API | $0 (free, far under quota) |
| Telegram Bot API | $0 (free) |
| Total | $5 to $20/month for the whole thing |
Compare that to a dedicated order-alert app plus a separate spreadsheet-sync app, each billed monthly and often per order or per contact. The n8n version replaces both for a flat fee, and it does not get more expensive as you add the next workflow to the same instance.
Get the Ecommerce Order Starter template
The full guide above is free to follow. If you would rather skip the build, download the ready-to-import n8n workflow, add your credentials, and be live in under five minutes. Import it on n8n Cloud or self-hosted.
Prefer it built and running for you? See our done-for-you automation service.
Frequently asked questions
Do I need to know how to code to automate my store with n8n?
No. Most ecommerce workflows use pre-built nodes you connect on a canvas: a trigger, a transform, and one or two actions. You only touch code for edge cases, and even then a Code node accepts short JavaScript snippets. The starter workflow in this guide has zero custom code.
Does n8n work with both Shopify and WooCommerce?
Yes. n8n ships dedicated Shopify and WooCommerce nodes, and anything not covered by a node you can reach through the HTTP Request node against the store REST API. Many merchants run one n8n instance across both platforms, which is one reason it beats platform-locked apps.
How much does it cost to run ecommerce automations on n8n?
Self-hosted n8n is free and runs on a small VPS for about 5 dollars a month with unlimited executions. n8n Cloud starts near 20 dollars a month. Either way you avoid stacking monthly fees for a separate app per task, which is where the real savings come from.
Will automating orders slow down my store checkout?
No. Order webhooks fire after checkout completes, so your automations run in the background on n8n and never sit in the shopper path. The customer sees the normal thank-you page while your logging and alerting happen a second or two later, out of view.
Can one workflow log an order and send a notification at the same time?
Yes. A single node can branch to two actions at once. In the starter template, the order-summary node feeds both a Google Sheets append and a Telegram message in parallel, so each new order is logged and alerted from one run without duplicating the trigger.