The flow
Starts it 1Logic 6Service 12
The steps in the order they run, from what starts it.
- 1Schedule TriggerSchedule triggerStarts it
- 2Http request (Delistings)Http RequestService
- 3HTTP Request (listings)Http RequestService
- 4Split ItemsCodeLogic
- 5Split Items1CodeLogic
- 6LimitLimitLogic
- 7Limit1LimitLogic
- 8Get a rowSupabaseService
- 9Get a row1SupabaseService
- 10IfIfLogic
- 11If1IfLogic
- 12Send a message(Delistings)DiscordService
- 13Send Delisting Alert To TelegramTelegramService
- 14Create Tweet DelistingTwitterService
- 15Send a message (new listings)DiscordService
- 16Send Listing Alert To TelegramTelegramService
- 17Create Tweet ListingTwitterService
- 18Store ID for future UpdatesSupabaseService
- 19Store ID for future updates1SupabaseService
How it's built
- Starts on
- A clock
- Steps
- 19, with 2 branches
- Size
- Medium: a working afternoon
- Connects to
- Discord, Supabase, Telegram, X
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Discord, Supabase, Telegram and X accounts. 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. 19 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 19 steps before you point it at anything that matters.