The flow
Starts it 2Logic 9Service 6
The steps in the order they run, from what starts it.
- 1Manual Start TriggerManual triggerStarts it
- 2Hourly Alert TriggerSchedule triggerStarts it
- 3Create Delivery LedgerData TableService
- 4Set Vinted Search ParametersSetLogic
- 5Validate Search SettingsCodeLogic
- 6Build Brand Search QueriesCodeLogic
- 7Start FetchCat Vinted SearchHttp RequestService
- 8Download Vinted Search ResultsHttp RequestService
- 9Normalize and Filter ListingsCodeLogic
- 10Check for Matching ListingsIfLogic
- 11Keep Undelivered ListingsData TableService
- 12Show No-Match DetailsCodeLogic
- 13Build Telegram Alert BatchCodeLogic
- 14Format Telegram MessagesCodeLogic
- 15Send New Listings to TelegramTelegramService
- 16Prepare Delivery RecordsCodeLogic
- 17Record Delivered ListingsData TableService
How it's built
- Starts on
- A clock
- Steps
- 17, with 1 branch
- 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. 17 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 17 steps before you point it at anything that matters.