Automation library · Alerts and monitoring

Proxmox system monitor - VM status, host resources & temperature

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

Medium

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

The flow

Starts it 1Logic 4Service 6

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

  1. 1Schedule Every 15minSchedule triggerStarts it
  2. 2Set VariablesSetLogic
  3. 3Proxmox LoginHttp RequestService
  4. 4Prepare AuthSetLogic
  5. 5API - VM ListHttp RequestService
  6. 6API - Node TasksHttp RequestService
  7. 7API - Node StatusHttp RequestService
  8. 8SSH - Get SensorsSshService
  9. 9Process DataCodeLogic
  10. 10Generate Formatted MessageCodeLogic
  11. 11Send Telegram ReportTelegramService

How it's built

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

Questions

What does it need to run?

An n8n account, plus your own Telegram 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.