PRTG Push Notifications

PRTG can send alerts through its notification system using Execute HTTP Action. That makes it a good fit for Signalgrid, because you can forward sensor and system events directly to the Signalgrid Push API and get them on your phone within seconds.

This is a simple setup for administrators who want mobile alerts for outages, warning states, failed checks, or important infrastructure changes without building a separate relay service.

Prerequisites

• A working PRTG installation with access to Notification Templates
• A Signalgrid account
• Your Signalgrid Client Key
• Your Signalgrid Channel Token
• Outbound HTTPS access from your PRTG server to https://api.signalgrid.co

How the Integration Works

PRTG can trigger an HTTP request when a notification event fires. If that request is sent to the Signalgrid Push API, the alert becomes a push notification.

In practice, the flow looks like this:

• PRTG detects a state change or threshold breach
• A notification template runs an HTTP action
• PRTG sends a request to the Signalgrid Push API
• Signalgrid delivers the alert to devices subscribed to your channel

Create a Notification Template in PRTG

In the PRTG web interface, create a new notification template and choose Execute HTTP Action as the delivery method.

The exact labels can vary slightly between PRTG versions, but the general path is:

• Open Setup
• Go to Account Settings
• Open Notification Templates
• Create a new notification template
• Enable Execute HTTP Action

Signalgrid Push API Endpoint

Use this Signalgrid endpoint for the notification action:

https://api.signalgrid.co/v1/push

The request should be sent as an HTTP POST request.

Recommended HTTP Action Settings

Depending on your PRTG version, the fields may be named slightly differently, but this is the recommended setup:

Example Request Body

A simple PRTG payload can look like this:

client_key=YOUR_CLIENT_KEY&channel=YOUR_CHANNEL_TOKEN&type=WARN&title=PRTG Alert&body=Sensor or device entered a warning state

This is enough to prove the integration works. Once that is working, you can replace the static text with PRTG placeholders that fit your notification style.

Suggested Placeholder Mapping

PRTG notification templates support placeholders for object names, status, and message content. The exact placeholder names depend on the PRTG editor and version, so use the variables available in your PRTG interface, but map them like this:

A practical finished payload often looks like this pattern:

client_key=YOUR_CLIENT_KEY&channel=YOUR_CHANNEL_TOKEN&type=WARN&title=[short PRTG event title]&body=[detailed PRTG event message]

Choosing the Notification Type

If your PRTG setup does not dynamically map severities, start with one of these defaults:

• WARN for warning and degraded states
• CRIT for hard failures and urgent outages
• SUCCESS for recovery or up-state notifications
• INFO for informational events

If you want one general-purpose PRTG template, WARN is a good default.

Using Critical Notifications Carefully

For truly urgent monitoring incidents, you can also include critical=true:

client_key=YOUR_CLIENT_KEY&channel=YOUR_CHANNEL_TOKEN&type=CRIT&critical=true&title=PRTG Critical Alert&body=Immediate action is required

Use this only for the alerts that should break through silent mode and Do Not Disturb on supported devices. If everything is marked critical, the useful urgency disappears fast.

Assign the Template to a Trigger

After saving the notification template, assign it to the sensors, devices, groups, or probes you want to monitor.

• Open the object you want to alert on
• Go to its Notification Triggers
• Add or edit a trigger
• Select your new Signalgrid / PRTG notification template

Test the Integration

Use PRTG's built-in notification test for the template if it is available in your version. Keep in mind that test notifications may send raw placeholder names instead of resolved values, which is normal for PRTG.

You can also verify the same request outside PRTG with a manual API call:

curl -X POST https://api.signalgrid.co/v1/push \
    -d "client_key=YOUR_CLIENT_KEY" \
    -d "channel=YOUR_CHANNEL_TOKEN" \
    -d "type=WARN" \
    -d "title=PRTG test notification" \
    -d "body=Manual test from the Signalgrid documentation page"

Troubleshooting