Quick overview
This workflow runs daily or on demand to read Proxmox VE cluster health (nodes, storages, backups, snapshots, and recent tasks), grades findings as OK/WARNING/CRITICAL, optionally posts a single alert to a configurable webhook endpoint, and returns the full report.
How it works
- Runs every morning at 7am on a schedule or when you POST to the manual webhook endpoint.
- Calls the Proxmox VE API to fetch cluster resources (nodes, guests, storages), guests not covered by any backup job, and recent cluster tasks.
- Filters for available backup storages and queries the Proxmox VE API for each storage’s backup file listing.
- Filters for non-template guests (excluding any configured IDs) and queries the Proxmox VE API for each guest’s snapshot list.
- Combines all retrieved data into a single health report, grading issues like offline nodes/storages, low backup coverage, stale backups, old snapshots, and failed tasks.
- Posts the report to the configured alert webhook when the status meets your alert threshold (or when forced to alert on OK).
- Fails the execution if any Proxmox data could not be read; otherwise returns the report JSON as the workflow output.
Setup
- Create a Proxmox VE user and API token with read-only permissions sufficient for cluster, VM/CT, backup, and datastore audit (and datastore allocate space if required to list backup files).
- In n8n, create an HTTP Header Auth credential with header name
Authorization and a PVEAPIToken=... value, and select it on all Proxmox HTTP Request nodes.
- In “Set Configuration Parameters”, set
api_url to your Proxmox API base URL and configure thresholds like backup_max_age_hours, snapshot_max_age_days, and storage warning/critical percentages.
- Set
alert_url to your target webhook (or leave it blank to disable alerts) and adjust alert_on/alert_when_ok to control when notifications are sent.
- If using the manual run, copy the “Run Now Webhook” URL and send a POST request to test end-to-end connectivity and output.