The flow
Starts it 1Logic 6Service 3
The steps in the order they run, from what starts it.
- 1Transit Schedule CheckSchedule triggerStarts it
- 2Define Transit URLsCodeLogic
- 3Split URLsSplit In BatchesLogic
- 4Scrape Schedule DataScrapegraph AiService
- 5Combine ResultsMergeLogic
- 6Process Transit DataCodeLogic
- 7Upsert Transit DataSupabaseService
- 8Has Delay?IfLogic
- 9Prepare Teams MessageCodeLogic
- 10Send Teams AlertMicrosoft TeamsService
How it's built
- Starts on
- A clock
- Steps
- 10, with 1 branch, 1 loop or waits
- Size
- Medium: a working afternoon
- Connects to
- Supabase
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Supabase 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. 10 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.
Before you run itNothing 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 10 steps before you point it at anything that matters.