This playbook uses PRTG, a third-party tool. We aim to keep these details accurate, but we can't guarantee they're always complete or up to date. For the most reliable information, refer to the PRTG HTTP API documentation and the Lansweeper PRTG connector documentation.
Lansweeper continuously discovers the physical and virtual assets on your network. PRTG only monitors devices it already knows about. An asset that exists in Lansweeper but not in PRTG gets no monitoring, so it generates no alert if something goes wrong with it.
This playbook covers 3 Flow Builder templates, built on the Flow Builder PRTG connector, that connect the two systems. You can find them in the Marketplace. Together, they create a PRTG device for each new Lansweeper asset, copy PRTG device data back into Lansweeper, and pause the PRTG device for any asset that Lansweeper no longer sees. Assets that Lansweeper discovers get monitored without manual work, and devices for retired assets stop sending alerts.
| Flow | What it does | Trigger |
|---|---|---|
| Auto-provision new PRTG device object | Creates a PRTG device for each new Lansweeper asset of the configured type | New Asset event |
| Enrich assets with PRTG device data | Copies PRTG device ID and location into Lansweeper, and optionally adds PRTG probe, tag, and group details to the asset Notes field | Schedule |
| Pause non-active PRTG device objects | Pauses the PRTG device linked to a Lansweeper asset once Lansweeper marks that asset non-active | Schedule |
All 3 flows link a Lansweeper asset to a PRTG device using a Lansweeper custom field named PRTG ID. Auto-provision new PRTG device object creates this field automatically if it doesn't already exist.
What you will need
Before you set up any of these flows, confirm you have:
- A Lansweeper site with Flow Builder enabled
- A PRTG server with API access: either an on-premises PRTG Network Monitor server or a PRTG Hosted Monitor instance
- HTTPS connectivity from Flow Builder to the PRTG server. An on-premises PRTG server must be reachable on its configured HTTPS port (443 by default).
- A PRTG API token for a service account, with write access for Auto-provision new PRTG device object and Pause non-active PRTG device objects, and read access for Enrich assets with PRTG device data
Auto-provision new PRTG device object
When Lansweeper discovers a new asset of the configured type, this flow checks PRTG for a matching device. If none exists, it creates one by cloning a template device, then writes the new PRTG device ID back to the PRTG ID custom field on the Lansweeper asset.
Use this flow to keep PRTG's device list up to date with Lansweeper's asset inventory, without manual data entry.
Auto-provision requirements
Beyond the requirements listed earlier, confirm you also have:
- A PRTG API token with write access to the target group
- At least 1 template device in PRTG to clone new devices from
- A PRTG group ID to hold the devices this flow creates
To find an object's ID in PRTG, open that device or group in the PRTG web interface and read the id= value from the browser address bar.
Configure Auto-provision new PRTG device object
Each flow instance handles one Lansweeper asset type. To set up an instance, configure:
- PRTG connection: server URL and API token for your PRTG instance
- Asset type: the Lansweeper asset type this instance watches, for example "Linux" or "Webserver"
- PRTG group ID: the PRTG group where the flow creates new devices
- PRTG tag: the tag this flow applies to devices it creates, and uses to scope its own searches
- Template device ID: the PRTG device to clone for this asset type
New devices stay paused in PRTG until someone resumes them manually. To start monitoring new devices right away, set Hold for Review to False in the flow.
Enrich assets with PRTG device data
Lansweeper holds asset inventory data. PRTG holds its own device details: which probe and group a device sits under, its tags, and its location in PRTG. This flow matches the two records and copies PRTG's device data into Lansweeper.
Use this flow to keep the PRTG ID custom field and asset location up to date, and to see PRTG context on the Lansweeper asset record.
Enrich requirements
Beyond the requirements listed earlier, confirm you also have:
- A PRTG API token with read access to the target group
- Existing PRTG devices in the target group, tagged with the tag this flow searches for, for example devices that Auto-provision new PRTG device object created
Configure Enrich assets with PRTG device data
To set up this flow, configure:
- PRTG connection: server URL and API token for your PRTG instance
- PRTG group ID: the PRTG group this flow searches for matching devices
- PRTG tag: the tag this flow uses to scope its device search
- Force replace notes: set to
Trueto overwrite the asset's Notes field with PRTG probe, tag, and group data on every run. Set toFalse, the default, to leave the Notes field alone - Schedule: how often the flow runs
This flow matches a Lansweeper asset to a PRTG device by comparing the asset's DNS name against the PRTG device's host value.
Pause non-active PRTG device objects
When Lansweeper stops seeing an asset in its scans for a set number of cycles, it marks the asset as non-active. Left alone, PRTG keeps polling the matching device and can generate false alerts for hardware that may no longer be on the network. This flow pauses the PRTG device instead, so PRTG stops alerting on it. It doesn't delete the device; deletion remains a manual step.
Pause requirements
Beyond the requirements listed earlier, confirm you also have:
- A PRTG API token with write access to the target devices
- Lansweeper assets with the
PRTG IDcustom field already set, for example by Auto-provision new PRTG device object
Configure Pause non-active PRTG device objects
To set up this flow, configure:
- PRTG connection: server URL and API token for your PRTG instance
- Schedule: how often the flow runs
This flow queries Lansweeper for assets with a state of "Non-active" that also have a PRTG ID value set, then pauses the matching PRTG device using that ID. It records the reason and date in the device's pause message. The default message reads "Lansweeper detects as non-active".
Summary
- Auto-provision new PRTG device object creates a PRTG device, paused by default, for each new Lansweeper asset of the configured type, and links the two records through the
PRTG IDcustom field. - Enrich assets with PRTG device data runs on a schedule to copy PRTG device ID, location, and optionally Notes field data, into matching Lansweeper assets.
- Pause non-active PRTG device objects runs on a schedule to pause the PRTG device linked to any Lansweeper asset that Lansweeper marks non-active.
- All 3 flows rely on the same
PRTG IDcustom field to link a Lansweeper asset to its PRTG device.