Automation library · Alerts and monitoring

Monitor server uptime with HTTP

Started by a clock, and works across n8n data table. 12 steps, 2 branches: a working afternoon to understand properly.

Medium

12 stepsMedium: a working afternoon
2Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 2Logic 7Service 3

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

  1. 1When clicking ‘Execute workflow’Manual triggerStarts it
  2. 2Schedule every minutesSchedule triggerStarts it
  3. 3configCodeLogic
  4. 4http_check_serverHttp RequestService
  5. 5db_get_latest_statusData TableService
  6. 6http_add_urlSetLogic
  7. 7MergeMergeLogic
  8. 8validate_statusIfLogic
  9. 9db_upsertData TableService
  10. 10if_more_than_intervalIfLogic
  11. 11send_notif_status_changeExecute WorkflowLogic
  12. 12send_notif_status_stillExecute WorkflowLogic

How it's built

Starts on
A clock
Steps
12, with 2 branches
Size
Medium: a working afternoon
Connects to
n8n data table
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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