Automation library · Alerts and monitoring

Public transit delay monitor with Microsoft Teams and Supabase

Started by a clock, and works across Supabase. 10 steps, 1 branch, 1 loop or waits: a working afternoon to understand properly.

Medium

10 stepsMedium: a working afternoon
1Branch: places the flow splits
1Loop or waits
1Service it connects to

The flow

Starts it 1Logic 6Service 3

The steps in the order they run, from what starts it.

  1. 1Transit Schedule CheckSchedule triggerStarts it
  2. 2Define Transit URLsCodeLogic
  3. 3Split URLsSplit In BatchesLogic
  4. 4Scrape Schedule DataScrapegraph AiService
  5. 5Combine ResultsMergeLogic
  6. 6Process Transit DataCodeLogic
  7. 7Upsert Transit DataSupabaseService
  8. 8Has Delay?IfLogic
  9. 9Prepare Teams MessageCodeLogic
  10. 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 it

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 10 steps before you point it at anything that matters.