Skip to main content
Triggr reads PRTG tables such as sensors, devices and messages, and acknowledges alarms, through PRTG’s classic HTTP API. Use it for PRTG Hosted Monitor, a cluster, or a PRTG without API v2; otherwise use PRTG.

​
Set up PRTG

1

Create a PRTG user for Triggr

In Setup > System Administration > User Accounts, add a user (Invite User on Hosted Monitor). Set User Type to Read-only user, with Allow user to acknowledge alarms if workflows acknowledge alarms, and a Primary Group that can see the objects your workflows read.
2

Create an API key

Signed in as that user, go to Setup > Account Settings > API Keys and select Add API Key (not the MultiBoard option). Set Access Level to Read access, or Acknowledge access to acknowledge alarms. Copy the key before you click OK; PRTG shows it only once.
3

Let Triggr reach PRTG

A self-hosted PRTG needs its HTTPS port reachable at a public address, with Triggr’s IP addresses allowed through any firewall.
See Paessler’s user accounts and API keys pages.

​
Connect it in Triggr

The Base Configuration serves workflows that run without a client.
1

Open the configuration

Go to Integrations > PRTG V1 and click Configure on the Base Configuration card.
The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button.
2

Enter the key and address

Paste the key into apiToken. In hostname, enter the web interface address with https:// and any non-443 port, such as https://prtg.example.com or https://yourcompany.my-prtg.com, with no path. Turn on Allow insecure TLS if PRTG uses its self-signed certificate, then click Save Configuration.
The PRTG V1 configuration window with apiToken and hostname fields, an Allow insecure TLS switch under Advanced, and a Save Configuration button.
To test it, run Get JSON with content set to sensors and columns set to objid,sensor,status.

​
Set up each client

Per-client integrations never fall back to the Base Configuration, so click Configure on each client’s row and enter its own hostname, apiToken and Allow insecure TLS. Triggr saves the hostname as the client’s prtgHostname variable. If one server monitors several clients, give each client its own PRTG user whose group sees only its part of the device tree.
The Per-Client Configuration card listing Acme Corp and Globex, each Not Configured with Admin Consent Not Required and a Configure button.

​
Use the actions

  • Get JSON and Get XML: content picks the table (sensors, devices, messages) and columns lists fields separated by commas, such as objid,group,device,sensor,status,message. See Paessler’s table reference.
  • Acknowledge Alarm: objectId is the sensor’s objid and acknowledgeMessage is the text PRTG shows.

​
Troubleshooting

Configure the client on the Per-Client Configuration card.
Check the configuration the workflow used (the client’s, if it ran for one) has the full key, and the key still exists under the Triggr user’s API Keys.
Set the key’s Access Level to Acknowledge access or higher, and check the user may acknowledge alarms.
Check hostname is a public address with https://, any non-443 port and no path, and your firewall allows Triggr’s IP addresses. For certificate errors, turn on Allow insecure TLS or install a trusted certificate.