Proxmox Push Notifications

Updated on November 20, 2026 Proxmox VE Documentation

Send Proxmox VE backup results and critical alerts to your phone
with a Webhook notification target and Signalgrid.

Send Proxmox notifications to your phone

Receive Proxmox VE backup results and other notification-system events on iPhone, Android, and the web. Configure Signalgrid as a Webhook notification target and use matchers to choose which events should reach your devices.

Prerequisites

  • A Proxmox VE installation with the Webhook target type under Datacenter → Notifications.
  • Permission to create notification targets and matchers.
  • A Signalgrid account with an iPhone, Android device, or web client registered to receive notifications.
  • Your Signalgrid client key and a channel token. Use the channel token rather than the channel name.
  • Outbound HTTPS access to https://api.signalgrid.co.

Create a Webhook target

Open Datacenter → Notifications, add a notification target and choose Webhook. Name it signalgrid and configure:

Setting
Value
URL
https://api.signalgrid.co/v1/push
Method
POST
Header name
Content-Type
Header value
application/x-www-form-urlencoded

Add the credentials as secrets

In the target's secrets section, add these entries. Proxmox stores target secrets separately in its protected notification configuration.

Secret name
Value
client_key
YOUR_CLIENT_KEY
channel
YOUR_CHANNEL_TOKEN

Replace the placeholders with your own credentials. Reference the secrets by name in the body template rather than copying their values into ordinary fields.

Configure the request body

Paste the following as a single line into the target's Body field:

Handlebars
client_key={{ url-encode secrets.client_key }}&channel={{ url-encode secrets.channel }}&title={{ url-encode title }}&body={{ url-encode message }}&type=INFO&critical=false

Proxmox fills in title and message from the notification event. Its url-encode helper escapes every dynamic value so backup details, punctuation and line breaks remain part of the correct form field.

Test the notification target

  • Save the target and select Test in the notification target list.
  • Check that the notification appears in the expected Signalgrid channel.
  • If the test fails, check the target URL, method, content type and secret names before creating matchers.

Route events with a notification matcher

  • Under Datacenter → Notifications, create or edit a notification matcher.
  • Select the signalgrid target.
  • Choose matching rules for the events and severities you want, such as backup notifications or warning and error events.
  • Save the matcher and trigger a controlled event to verify the route.

The target test checks delivery. Real notifications also need an enabled matcher that selects this target. Review existing matchers so an event reaches the intended destinations.

Enable backup notifications

Open the backup job settings and select the notification mode that uses the notification system. A job configured for legacy sendmail uses its email route instead of these notification targets. Run a controlled backup and check both its task result and the mobile notification.

Separate routine and critical alerts

Use the basic target for routine backup results. For urgent failures, create another Webhook target with the same URL, headers and secrets, but use this body:

Handlebars
client_key={{ url-encode secrets.client_key }}&channel={{ url-encode secrets.channel }}&title={{ url-encode title }}&body={{ url-encode message }}&type=CRIT&critical=true

Route only error events that need immediate attention to this critical target. Keep routine and urgent matcher conditions separate if you want one mobile notification per event.

Send critical alerts

For urgent incidents, set critical to true and type to CRIT. These are separate settings: the visual notification type alone does not enable critical delivery. Critical notifications require a Single or Teams subscription and the appropriate device permissions. See Critical Notifications for iOS Critical Alerts and Android notification settings. Keep routine results non-critical.

Troubleshooting

  • Webhook target is unavailable: check whether your Proxmox version supports this notification target type.
  • Test request is rejected: verify the form content type, POST method and exact secret names client_key and channel.
  • Test arrives but backup events do not: check the backup notification mode and matcher rules.
  • Unexpected notification content: inspect the event title and message and keep the URL-encoding helpers in place.
  • No critical sound: check the paid subscription and device permissions described in Critical Notifications.

Official documentation