Catch Amazon MAP price breaches with Bright Data, Data Tables and Telegram
Ready for 3.0Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.
What this workflow does
This workflow has 20 nodes and runs on a schedule (every day at 07:00). Along the way it connects Telegram.
How it runs
Trigger: On a schedule (every day at 07:00).
- Settings (Edit Fields (Set)): sets 5 fields: max_terms, results_per_term, price_tolerance_percent…
- Read Your Price Policy (Data table): get
- Build The Watch List (Code): runs custom JavaScript code
- One Product Line At A Time (Loop Over Items (Split in Batches)): loops over the items in batches
- Find The Breaches (Code): runs custom JavaScript code
- Search Amazon For This Line (HTTP Request): calls an HTTP API (POST)
- Anything To Chase? (If): checks a condition and branches into true / false
- Check The Job Started (Code): runs custom JavaScript code
- One Breach At A Time (Split Out): splits a list into separate items
- Wait: waits 20 seconds
…plus 8 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (11)
- Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - Data table
n8n-nodes-base.dataTable - Code
n8n-nodes-base.code - Loop Over Items (Split in Batches)
n8n-nodes-base.splitInBatches - HTTP Request
n8n-nodes-base.httpRequest - Wait
n8n-nodes-base.wait - If
n8n-nodes-base.if - No Operation, do nothing
n8n-nodes-base.noOp - Split Out
n8n-nodes-base.splitOut - Telegram
n8n-nodes-base.telegram
From the author
Quick overview This workflow runs every morning to check Amazon listings via Bright Data against your MAP policy stored in n8n Data Tables, logs detected breaches, and sends a Telegram digest when unauthorized sellers or under-floor prices are found. How it…