Automation library · Data collection

Public transit delay tracker with Mailgun and ClickUp

Started by a clock, and works across ClickUp. 11 steps, 1 branch: a working afternoon to understand properly.

Medium

11 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Logic 7Service 3

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

  1. 1Schedule – Check TransitSchedule triggerStarts it
  2. 2Define Target URLsCodeLogic
  3. 3Scrape Transit DataScrapegraph AiService
  4. 4Parse Delay DataCodeLogic
  5. 5Check Significant DelayIfLogic
  6. 6Build Email AlertCodeLogic
  7. 7Prepare ClickUp TaskSetLogic
  8. 8Send Mailgun AlertMailgunService
  9. 9Create ClickUp TaskClick UpService
  10. 10Combine ResultsMergeLogic
  11. 11Final LogCodeLogic

How it's built

Starts on
A clock
Steps
11, with 1 branch
Size
Medium: a working afternoon
Connects to
ClickUp
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own ClickUp 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. 11 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 11 steps before you point it at anything that matters.