Automation library · Alerts and monitoring

Automated website uptime monitor with GitHub

Started by a clock, and works across GitHub and Gmail. 10 steps, 2 branches: a working afternoon to understand properly.

Medium

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

The flow

Starts it 1Logic 3Service 6

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

  1. 1Schedule TriggerSchedule triggerStarts it
  2. 2HTTP RequestHttp RequestService
  3. 3Switch - status codeSwitchLogic
  4. 4Template HTML CodeCodeLogic
  5. 5Send a notification mailGmailService
  6. 6Extract from File - Generated HTMLExtract From FileService
  7. 7Get existing index.html fileGithubService
  8. 8Extract from existing File (github)Extract From FileService
  9. 9If - Compare existing HTML file with generated HTMLIfLogic
  10. 10Update Index.html fileGithubService

How it's built

Starts on
A clock
Steps
10, with 2 branches
Size
Medium: a working afternoon
Connects to
GitHub, Gmail
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own GitHub and Gmail accounts. 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.