The flow
Starts it 1Logic 13Service 6
The steps in the order they run, from what starts it.
- 1Check Every MorningSchedule triggerStarts it
- 2SettingsSetLogic
- 3Read Your Price PolicyData TableService
- 4Build The Watch ListCodeLogic
- 5One Product Line At A TimeSplit In BatchesLogic
- 6Find The BreachesCodeLogic
- 7Search Amazon For This LineHttp RequestService
- 8Anything To Chase?IfLogic
- 9Check The Job StartedCodeLogic
- 10One Breach At A TimeSplit OutLogic
- 11Nothing To ReportNo OpLogic
- 12Wait For AmazonWaitLogic
- 13Log The BreachesData TableService
- 14Check The SnapshotHttp RequestService
- 15Build The AlertCodeLogic
- 16Count The PollsCodeLogic
- 17Send The AlertTelegramService
- 18Listings Ready?IfLogic
- 19Download The ListingsHttp RequestService
- 20Read Every OfferCodeLogic
How it's built
- Starts on
- A clock
- Steps
- 20, with 2 branches, 2 loops or waits
- Size
- Medium: a working afternoon
- Connects to
- Telegram, n8n data table
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Telegram account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 20 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 20 steps before you point it at anything that matters.