Shopify product auto-tagging with n8n keeps your catalog organized without anyone remembering to do it. The moment a new product is created, a webhook fires, a rule step builds tags from the product’s vendor, type, and price, and the product updates itself. Consistent tags are what power your automatic collections, storefront filters, and every workflow that routes products by category, so getting them right on every product, every time, quietly makes the rest of your store work better.
What it does
Tags are the connective tissue of a Shopify store. Automatic collections build from them, storefront filters read them, and downstream automations branch on them. But tags are only useful if they are applied consistently, and manual tagging never is. Someone forgets the vendor tag, someone types “mid range” one day and “mid-range” the next, and your filters quietly break.
This workflow removes the human from that loop. Whenever a product is created, it reads the product and assigns a clean, consistent set of tags: the vendor, the product type, and a price band worked out from the lowest variant price. It merges those with any tags already on the product, removes duplicates, and writes them back. A new product goes from untagged to fully classified in a second, for example:
Product: Merino Crew Sweater
Vendor: Acme
Type: Sweater
Price: from 49.00
Tags: Acme, Sweater, mid-rangeEvery product gets the same treatment, so your collections and filters can trust the tags underneath them.
Why it beats the default
The manual default is tagging each product by hand at upload time, which is exactly when you are busy writing the description and setting the price, so tags get skipped or done inconsistently. Shopify has no built-in rule engine that tags products by their own attributes, so there is nothing catching the misses.
An automated rule is consistent by definition. The same logic runs on every product, so “mid-range” is always spelled the same way and the vendor tag is never forgotten. That consistency is what lets an automatic collection like “All premium items” or a storefront filter by vendor actually work. Compared with Shopify Flow, which is limited to Shopify Plus, n8n runs this on any plan and lets you tag on any rule you can express in a line of code.
It also composes with the rest of your catalog work. Bulk uploads, supplier feeds, and manual additions all pass through the same tagging, so however a product enters your store, it comes out classified the same way.
What you need
- A Shopify store on any plan, with an admin login that can create a custom app.
- An n8n instance, either n8n Cloud or self-hosted (version 1.0 or newer).
- A Shopify Admin API access token with read and write access to products, created through the 2026 Shopify Dev Dashboard method. New to this? Follow connect Shopify to n8n (2026 guide) first.
- A tagging scheme in mind: which attributes matter and where your price bands sit.
Build time is about 15 minutes from scratch, or a couple of minutes if you import the ready-made template below and adjust the rules.
Node-by-node list
Three nodes, in a straight line. Here is each one and what it does.
| # | Node | Type | Job |
|---|---|---|---|
| 1 | New Shopify product | shopifyTrigger |
Fires on the products/create webhook for every new product, delivering the full product payload. |
| 2 | Build tags | code |
Reads the vendor, type, and lowest variant price, works out the tags and price band, and merges them with existing tags. |
| 3 | Update product tags | shopify |
Writes the merged tag list back to the product. |
How it works
[New Shopify product] (products/create webhook)
|
v
[Build tags] (vendor + type + price band, merged with existing)
|
v
[Update product tags] (write tags back to the product)
Step-by-step build
- Create a new workflow in n8n and name it “Shopify product auto-tagging.”
- Add a Shopify Trigger node. Set Authentication to Access Token and attach your credential. Set the Topic to
products/create. When you activate the workflow, n8n registers this webhook in your store for you. - Add a Code node named “Build tags” after it, in Run Once for Each Item mode. It reads the product, adds the vendor and product type as tags, and assigns a price band from the lowest variant price. The bands are two numbers you can change:
if (min < 25) band = 'budget'; else if (min <= 100) band = 'mid-range'; else band = 'premium';It merges the new tags with the product’s existing tags and removes duplicates, returning the product id and the final tag string.
- Add a Shopify node named “Update product tags” after it. Resource Product, Operation Update. Set Product ID to
{{ $json.productId }}. Under Update Fields add Tags with the value{{ $json.newTags }}, which writes the merged list back without losing anything. - Save, then create a test product in Shopify. Confirm it picks up the vendor, type, and price-band tags, then toggle the workflow Active so every new product is tagged automatically.
Tip: to classify your existing catalog too, duplicate this workflow and replace the trigger with a Schedule Trigger plus a Shopify Get Many products step. The same Build tags logic then runs across every product. Run it once to backfill, then rely on the webhook version for anything new.
Common mistakes
- Overwriting existing tags. A product update replaces the whole tag list. The Build tags step merges with the current tags first, so keep that merge or you erase manual tags.
- Reading a single variant’s price. A product can have several variants at different prices. The step takes the lowest variant price for the band, so a product with a cheap size is not miscategorized as premium.
- Inconsistent band spelling. If you hand-edit the band names, spell them identically everywhere, since a collection filtering on
mid-rangewill not matchmid range. - Read-only token. Tagging is a write. If your Shopify token cannot write products, the read works but the update fails. Grant write access to products on the credential.
- Expecting old products to update. The
products/createwebhook only fires for new products. Use the schedule variant above to tag the catalog you already have.
Cost at realistic volume
This workflow runs inside free tiers at any catalog size. The Shopify Admin API is included with your plan, and one tag write per new product is well within rate limits. There is no third-party service to pay for, since the tags live on Shopify.
On n8n, each new product runs three quick steps. Even a store adding hundreds of products a month runs this for nothing on n8n Cloud’s entry plans and free on self-hosted n8n. The payoff is a catalog that tags itself correctly forever, which is the foundation your collections, filters, and other automations quietly depend on.
Download the ready-to-import template
The guide above is free to follow, and building it by hand takes about 15 minutes. The template is the same validated workflow as a single .json import, so you skip the build and just add your credentials and rules. Prefer it done for you? Our done-for-you setup service installs and tests it on your instance.
Instant download · Works on n8n Cloud and self-hosted
FAQ
What tags does it assign?
Out of the box, three: the product’s vendor, its product type, and a price band of budget, mid-range, or premium based on the lowest variant price. The rules live in one small Code step, so you can add, remove, or rename any of them. The point is consistent tags applied the same way to every product.
Will it wipe my existing product tags?
No. The workflow reads the product’s current tags, adds the new ones, and removes duplicates before writing back. Anything you tagged by hand stays. A product that already has a seasonal tag keeps it and simply gains the vendor, type, and price-band tags on top.
Can I tag existing products, not just new ones?
Yes. Swap the products/create trigger for a Schedule Trigger plus a Shopify Get Many products step, and the same tagging logic runs across your whole catalog. Run it once to backfill every product, then keep the webhook version active so new products are tagged the moment you add them.
How do I change the price bands?
The thresholds are two numbers in the Code step: under 25 is budget, 25 to 100 is mid-range, and above is premium. Change those numbers to your own price points, or add more bands. Because it reads the lowest variant price, a product with a cheap size still lands in the right band.
Can I tag by other rules, like a title keyword?
Yes. The Code step has the full product object, so you can add rules on the title, SKU, weight, tags, or any field. A line that adds a sale tag when the title contains clearance, or an oversized tag above a weight, is a couple of lines. The vendor, type, and band rules are just a starting set.