Windows - Maintenance Tasks - Tag Automox Devices with Lansweeper Data

What the Lansweeper data tagger does

This Automox Worklet™ creates a bidirectional inventory sync between your Automox organization and Lansweeper Cloud instance. The Worklet uses the Lansweeper GraphQL API to pull endpoint asset information, then queries your Automox organization through the Automox API to locate matching endpoints by serial number.

Once matching endpoints are found, the Worklet automatically applies configurable Lansweeper fields as tags to your Automox endpoints. You specify which Lansweeper fields to extract (manufacturer, model, location, department, branch office, building, domain, FQDN, IP address, user name, BitLocker recovery key status, and others), and the Worklet applies those values as tags.

The Worklet executes the command "Get-Variable".

The Worklet preserves all existing Automox tags and adds Lansweeper data as new tags, verifying no tag data is lost during synchronization. It automatically deduplicates tags to prevent duplicate tag values on endpoints.

Why synchronize Lansweeper data with Automox tags

Many IT Operations teams use both Lansweeper and Automox to manage their endpoint inventory. Maintaining tag consistency between platforms is time-consuming when done manually. By automating tag synchronization, you verify that endpoint metadata stays current in Automox without requiring duplicate data entry.

Synchronized tags enable better endpoint targeting in Automox. If your Lansweeper instance maintains detailed department, location, or manufacturer information, syncing that data as Automox tags allows you to create more advanced Worklet deployment policies. You can target worklets to specific departments, buildings, or hardware types using the synchronized tag data.

Using Lansweeper data for tagging also improves your Automox reporting and analytics. Tags become searchable metadata that helps you quickly identify endpoints by business attributes rather than only by OS, IP address, or hostname.

How Lansweeper data tagging works

1. Evaluation phase: Queries the Lansweeper GraphQL API for all assets in your specified site ID, retrieving configurable asset fields. Then queries your Automox organization for all endpoints, storing their serial numbers and tag information. Compares serial numbers from both platforms to identify which endpoints exist in both systems. If matching endpoints are found, triggers remediation.

2. Remediation phase: Iterates through each matched endpoint and extracts the Lansweeper fields you specified in the configuration. Combines those extracted field values with existing Automox tags, removes duplicates, and applies the deduplicated tag list to the endpoint using the Automox endpoint tagging API. All existing tags are preserved and new Lansweeper-sourced tags are added.

Lansweeper tagging requirements

• Lansweeper Cloud instance (Starter, Pro, or Enterprise edition)

• Lansweeper Cloud Personal Application configured and API token generated

• Lansweeper Site ID for the specific site to query

• Automox API key with endpoint management permissions

• Automox Organization ID (OrgID)

• All four API credentials must be configured as Automox Shared Secrets: axApiKey, axOrgID, lsToken, lsSiteID

• Endpoints must have matching serial numbers in both Lansweeper and Automox for synchronization to occur

• Worklet configured to run on a single host endpoint using endpoint targeting (recommended for API consistency)

• Acceptable Lansweeper fields for tagging: assetUnique, bitLockerRecoveryKeys, branchOffice, building, department, description, domain, fqdn, ipAddress, lastPatched, location, mac, manufacturer, model, name, serialNumber, subType, type, typeGroup, url, userDomain, userName

Expected tag state after synchronization

After the Worklet completes successfully, matched endpoints will display new tags in the Automox console that correspond to the Lansweeper fields you configured. You can verify this change by checking Windows Settings or the relevant system configuration. For example, if you specified manufacturer and model as your tagging fields, each matched endpoint will have tags like "Dell" (manufacturer) and "OptiPlex 7090" (model) applied.

All previously existing Automox tags will remain intact. The Worklet only adds new tags from Lansweeper; it never removes your existing tag structure. When you query endpoints using tags in Automox (such as for endpoint targeting), you can now use the synchronized Lansweeper field values to create deployment policies based on physical location, department, hardware manufacturer, or any other Lansweeper asset field you included in the synchronization.