Automation library · Alerts and monitoring

Daily London traffic alert email with Tfl API

Started by a clock, and works across Gmail and Google Sheets. It hands the judgement calls to OpenAI. 10 steps: a working afternoon to understand properly.

MediumCalls a model: OpenAI

10 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 1Model 1Logic 5Service 3

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

  1. 17am TriggerSchedule triggerStarts it
  2. 2TfL Roads APIHttp RequestService
  3. 3Parse XML to JSONXmlLogic
  4. 4Split DisruptionsSplit OutLogic
  5. 5Filter Out Low InterestFilterLogic
  6. 6Store In databaseGoogle SheetsService
  7. 7AggregateAggregateLogic
  8. 8Message a model1Open AiModel
  9. 9HTML Email DesignerCodeLogic
  10. 10Send Traffic UpdateGmailService

How it's built

Starts on
A clock
Steps
10
Size
Medium: a working afternoon
Connects to
Gmail, Google Sheets
Model
OpenAI

Questions

What does it need to run?

An n8n account, plus your own Gmail and Google Sheets accounts, and a key for OpenAI. You connect your own accounts after importing it; none are included.

What starts it?

It starts on a clock.

Does it use AI?

Yes. It calls OpenAI. Model calls are billed by the provider, not by n8n.

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.