Copy page

Lansweeper

Vulnerabilities

Fetches vulnerability records from Lansweeper Cloud, including CVE details, risk scores, and affected asset information.

Sync Type: Full Synchronization

Prerequisites

Before connecting Monad to Lansweeper, you need:

1. An active Lansweeper Cloud account with access to the sites you want to collect vulnerability data from.
2. A Personal Access Token with permission to read vulnerability data from the target sites.

Authentication

Lansweeper uses Personal Access Tokens (PATs) to authenticate API requests.

Creating a Personal Access Token

1. In your Lansweeper Site, select Settings (bottom-left corner).

   If you are using the new Lansweeper Platform Experience, select your profile image in the top-right corner, then select Account settings.

2. Select Developer tools → API clients → Add new API client.
3. Select Personal Access Token.
4. Enter an API client name and optionally a description.
5. From the Integrations dropdown, select Other and enter a custom integration name (e.g., monad).
6. Select an expiration time for the token.
7. Select which sites you want to grant API access to.
8. Copy the generated token to your clipboard — it is only shown once.

Refreshing a Token

1. In your Lansweeper Site, select Settings (bottom-left corner).
2. Select Developer tools.
3. Select your PAT client from the list.
4. Select Refresh token → Yes.
5. Copy your token to your clipboard, then select Done.

Configuration

The following configuration defines the input parameters.

Settings

Setting	Type	Required	Description
Cron	string	Yes	Cron expression defining how often the full vulnerability inventory is re-listed (5-field, standard syntax).

Secrets

Secret	Type	Required	Description
Personal Access Token	secret	Yes	Long-lived bearer token for the Lansweeper API. Obtain it from Lansweeper Cloud Settings → Developer tools.

Troubleshooting

Common Issues

1. Authentication Errors (401 / 403)

   • Confirm the Personal Access Token is correct and has not been revoked.
   • Verify the token was copied in full with no extra whitespace.
   • Regenerate the token in Lansweeper Cloud Settings → Developer tools if needed.

2. No Sites Returned

   • Ensure the Lansweeper account associated with the token has access to at least one site.
   • Check within Lansweeper Cloud that the account is authorized for the target sites.

3. Empty Results

   • Confirm that the target sites have vulnerability data in Lansweeper Cloud.
   • Check the pipeline logs for any parse errors on the API response.

4. The Same Records Appear on Every Run

   • This is expected. This is a full-synchronization input: each scheduled run re-lists the complete vulnerability inventory for every authorized site and forwards all of it.

Related Articles

• Lansweeper Data API Quickstart
• Lansweeper Vulnerabilities API Reference
• Lansweeper Vulnerability Management Guide

Sync frequency

This input runs on the Cron schedule you configure — there is no default polling cadence, and a schedule is required. On each tick it fetches a full snapshot of vulnerabilities for every authorized site. See Input Sync Frequency for details.