---
title: "PRTG Connector | Lansweeper Platform"
slug: "prtg-connector"
description: "Use the PRTG connector in Flow Builder to list, create, and update PRTG devices, read sensor status, and pause or resume monitoring with an API token."
status: "new"
updated: 2026-10-02T13:51:31Z
published: 2026-10-02T13:51:31Z
canonical: "docs.lansweeper.com/prtg-connector"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lansweeper.com/llms.txt
> Use this file to discover all available pages before exploring further.

# PRTG Connector

Note on third‑party tools

              

We aim to provide accurate and helpful details about third‑party tools, but we can’t guarantee that this information is always complete or up to date. If you notice any discrepancies, feel free to share them in the feedback section below. For the most reliable information, please always refer to the third‑party tool’s official documentation.

[PRTG Network Monitor](https://www.paessler.com/prtg) is a network monitoring solution from Paessler that tracks the availability, health, and performance of devices and services. This component allows listing, creating, and updating devices, listing groups and sensors, reading live sensor details, and pausing or resuming monitoring in a PRTG server.

## API Documentation

This component was built using the [PRTG HTTP API](https://www.paessler.com/manuals/prtg/http_api).

## Connections

### API Key

Authenticate requests to PRTG using an API token. PRTG is stateless, so the token is sent on every request as the `apitoken` query parameter.

#### Prerequisites

- A PRTG Network Monitor (on-premises) or PRTG Hosted Monitor instance.
- HTTPS connectivity from Flow Builder to the PRTG server. An on-premises PRTG server must be reachable from Flow Builder on its configured HTTPS port (443 by default).
- A PRTG user account (ideally a scoped service account) with API access. To create or update devices, the account needs write access to the target device group.

#### Setup Steps

1. Log in to the PRTG web interface.
2. Open your account settings and go to the **API Keys** section.
3. Create an API key for the service account.
4. Copy the generated token.

Enter the PRTG server URL and the API token into the connection configuration.

| Input | Comments | Default |
| --- | --- | --- |
| Server URL | Full base URL of the PRTG core server, including protocol, for example `https://prtg.acme.com`. Don't include a trailing `/api`, because it's appended automatically. |  |
| API Token | PRTG API token for a scoped service account, sent as the `apitoken` query parameter on every request. Generate it in the PRTG web UI under your user account settings. |  |
| Verify SSL Certificate | Leave on for normal use. Turn off only for on-premises PRTG installs that use a self-signed certificate. | true |

## Triggers

This connector doesn't define any triggers. Use the built-in [Schedule Trigger](/docs/schedule-trigger-connector) to run flows on a schedule, for example a periodic provisioning and enrichment sync.

## Actions

### List Devices

List monitored devices, optionally filtered by group or tag.

| Input | Comments | Default |
| --- | --- | --- |
| PRTG Connection | The PRTG connection to use. |  |
| Group ID | Optional. Restrict to devices under this group (parent) ID. |  |
| Tag Filter | Optional. Restrict to devices carrying this tag. |  |
| Columns | Comma-separated list of PRTG columns to return. | objid,name,host,group,probe,tags,location |

### List Groups

List groups in the PRTG object tree.

| Input | Comments | Default |
| --- | --- | --- |
| PRTG Connection | The PRTG connection to use. |  |
| Columns | Comma-separated list of PRTG columns to return. | objid,name,parentid |

### List Sensors for Device

List the sensors attached to a device.

| Input | Comments | Default |
| --- | --- | --- |
| PRTG Connection | The PRTG connection to use. |  |
| Device ID | The device (parent) ID whose sensors should be listed. |  |
| Columns | Comma-separated list of PRTG columns to return. | objid,name,status,message,lastvalue,probe,group,device |

### Get Sensor Details

Get detailed live status for a sensor by its sensor ID (not a device ID).

| Input | Comments | Default |
| --- | --- | --- |
| PRTG Connection | The PRTG connection to use. |  |
| Sensor ID | A sensor ID. Use **List Sensors for Device** first to resolve the sensor IDs for a device. |  |

### Create Device

Clone a template device, set its properties, and start monitoring. PRTG can't create a device from scratch through the API, so this action duplicates an existing template device, applies the requested properties, and then resumes monitoring unless the device is held for review.

| Input | Comments | Default |
| --- | --- | --- |
| PRTG Connection | The PRTG connection to use. |  |
| Template Device ID | ID of an existing device to clone. |  |
| Name | Name of the new device. |  |
| Host | Optional. IP address or hostname of the new device. |  |
| Target Group ID | ID of the group the new device is created in. |  |
| Location | Optional. Location to set on the new device. |  |
| Tags | Optional. Space-separated tags. |  |
| Hold for Review | When true, the cloned device stays paused instead of being resumed. | false |

### Update Device Properties

Update the name, host, location, or tags on a device. Each provided property is applied with a separate call.

| Input | Comments | Default |
| --- | --- | --- |
| PRTG Connection | The PRTG connection to use. |  |
| Device ID | ID of the device to update. |  |
| Name | Optional. New device name. |  |
| Host | Optional. New IP address or hostname. |  |
| Location | Optional. New location. |  |
| Tags | Optional. Space-separated tags. |  |

### Pause Object

Pause monitoring of a device, group, or sensor.

| Input | Comments | Default |
| --- | --- | --- |
| PRTG Connection | The PRTG connection to use. |  |
| Object ID | Numeric PRTG object ID (objid) of the device, group, or sensor to pause. |  |
| Pause Message | Optional note shown against the paused object. |  |

### Resume Object

Resume monitoring of a paused device, group, or sensor.

| Input | Comments | Default |
| --- | --- | --- |
| PRTG Connection | The PRTG connection to use. |  |
| Object ID | Numeric PRTG object ID (objid) of the device, group, or sensor to resume. |  |

### Raw Request

Send an HTTP request to any PRTG API endpoint not covered by a dedicated action. The API token and SSL setting from the connection are applied automatically.

| Input | Comments | Default |
| --- | --- | --- |
| PRTG Connection | The PRTG connection to use. |  |
| Method | HTTP method. Most PRTG API endpoints use GET. | GET |
| Path | Path relative to `{Server URL}/api`, for example `/scannow.htm` or `/table.json`. |  |
| Query Parameters | Optional. Additional query parameters. The `apitoken` is added automatically. |  |
| Body | Optional. Request body for POST requests. |  |

## Data Sources

### Select Group

Fetch PRTG groups and present them as a dropdown for use in config pages.

| Input | Comments | Default |
| --- | --- | --- |
| PRTG Connection | The PRTG connection to use. |  |

### Select Device

Fetch PRTG devices and present them as a dropdown for use in config pages.

| Input | Comments | Default |
| --- | --- | --- |
| PRTG Connection | The PRTG connection to use. |  |