Product Research · Blog post · source Aug 5, 2026
Nightly Variant Price Tracking with n8n and SP-API
Compare my prices against competitors across dozens of child ASIN variants every day
He says it runs with no manual work and no browser extensions.
Per source Self-reported by the source, not independently verified.
Copy-paste prompt
Design an n8n workflow that runs daily at 2 AM: read a Google Sheet of my parent ASINs and competitor parent ASINs; for each, use SP-API Catalog Items to list child ASINs and their size attribute; use the Product Pricing API to get each child's current price; compute price per [unit]; and append one dated row per size with my price and each competitor's price. Never overwrite earlier rows. List the SP-API roles I need.
The source didn't publish its exact prompt. We wrote this starter so you can try the same workflow. Replace anything in [brackets].
What they did
A seller of gold chains built a self-hosted n8n workflow that runs every day at 2 AM: it reads product listings from Google Sheets, calls the Amazon SP-API for live pricing, walks parent/child ASIN relationships across 96+ variants, picks the 22" chain variant in each size from 1mm to 10mm, extracts price, gold weight and price per gram, and writes his listings and competitors' side by side back to the sheet.
How it went
He says it runs with no manual work and no browser extensions. The hardest part was that the catalog API returns variants as child ASINs, so each has to be fetched individually, mapped to the right size column and written without overwriting earlier data, which 'took serious debugging to get right.'
We only report what the source says. Results are self-reported unless noted.
Worth knowing
A LinkedIn build post that also offers to build the same for others. No results on pricing decisions are shared. The child-ASIN mapping problem applies to any variation-heavy catalog.