Automation library · Alerts and monitoring

Monitor school admission updates with Gemini

Started by a clock, and works across Email. It hands the judgement calls to Gemini. 11 steps, 1 branch, 2 loops or waits: a working afternoon to understand properly.

MediumCalls a model: Gemini

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

The flow

Starts it 1Model 1Logic 7Service 2

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

  1. 1Daily TriggerCronStarts it
  2. 2Shortlisted SchoolsCodeLogic
  3. 3Split In BatchesSplit In BatchesLogic
  4. 4Get Website ContentHttp RequestService
  5. 5Append school NameMergeLogic
  6. 6Clean HTMLCodeLogic
  7. 7Are admissions OpenGoogle GeminiModel
  8. 8Parse LLM responseCodeLogic
  9. 9IfIfLogic
  10. 10Send emailEmail SendService
  11. 11Continue LoopSplit In BatchesLogic

How it's built

Starts on
A clock
Steps
11, with 1 branch, 2 loops or waits
Size
Medium: a working afternoon
Connects to
Email
Model
Gemini

Questions

What does it need to run?

An n8n account, plus your own Email account, and a key for Gemini. 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 Gemini. Model calls are billed by the provider, not by n8n.

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.