Playbook: Enrich Lansweeper Asset Intelligence with Jamf Pro

Lansweeper's network discovery excels at finding Apple devices on your network. What it cannot see is what Jamf Pro knows about them: whether the device is enrolled in mobile device management (MDM), when its warranty expires, or whether it belongs to someone who works remotely and rarely connects to the corporate network.

This playbook covers 6 Flow Builder workflows that close that gap: 4 enrich or create Lansweeper assets from Jamf Pro data, and 2 give you a safe way to reverse any assets they create automatically.

What you will need

Before you start, make sure you have:

• A Lansweeper site with Flow Builder enabled
• A Jamf Pro cloud instance (jamfcloud.com)
• Admin access to Jamf Pro to create an API client
• Admin access to Lansweeper to create custom fields and configure Flow Builder connections
• For the mobile device creation workflow: iPad and iPhone asset types already set up in Lansweeper (see Workflow 4)

Part one: Setting up the Jamf API credentials

Jamf Pro uses OAuth 2.0 client credentials to control application programming interface (API) access. You will create a dedicated API role and client for this integration.

Step 1: Create the API role

1. In Jamf Pro, go to Settings > System > API Roles and Clients.
2. Select the API Roles tab and select New.
3. Give the role a clear name ("Lansweeper Flow Builder" works well).
4. Assign 2 privileges to the role: Read Computers and Read Mobile Devices. These are the only privileges the workflows need: they only read from Jamf and write to Lansweeper, never the other way round.
5. Save the role.

Step 2: Create the API client

1. Still in Settings > System > API Roles and Clients, select the API Clients tab and select New.
2. Give the client a name. "Lansweeper Flow Builder" again is consistent.
3. Assign the API role you just created.
4. Set an appropriate token expiry. The default (30 minutes) is fine. Flow Builder requests a new token automatically on each run.
5. Select Enable API Client, then Save.
6. On the next screen, select Generate Client Secret. Copy both the Client ID and the Client Secret. You will need them in Flow Builder. The secret is only shown once.

Part two: Setting up the Flow Builder connection

With the Jamf API client in place, create a named connection in Flow Builder.

Go to Flow Builder > Connections and create a new connection of type Jamf Client Credentials (part of the Jamf connector). Enter:

• Host URL: your Jamf Pro instance URL (for example, https://yourcompany.jamfcloud.com)
• Client ID: from the API client you created
• Client Secret: from the API client you created

Give the connection a recognizable name. "Jamf Pro" is the convention used in the workflows. This connection is reusable: all 6 workflows reference the same named connection.

Part three: The 6 workflows

The 6 workflows split into 2 groups. The first group enriches assets already in Lansweeper or creates new ones. The second group cleans up any assets the first group imported automatically.

Recommended order of deployment

1. Workflow 1: enrich Mac computers already in Lansweeper
2. Workflow 2: enrich mobile devices already in Lansweeper
3. Workflow 3: create asset records for Macs known to Jamf but not yet in Lansweeper
4. Workflow 4: create asset records for mobile devices known to Jamf but not yet in Lansweeper

Run the enrichment workflows (1 and 2) before the creation workflows (3 and 4). Enrichment writes the serial number back to devices Lansweeper already knows about, so the creation workflows correctly skip them instead of creating duplicates.

You can run the clean-up workflows (5 and 6) at any point after you use Workflows 3 or 4.

Workflow 1: Enrich Apple Computers with Jamf Pro Details

Purpose: matches Mac computers already in Lansweeper against Jamf Pro by serial number, then writes Jamf's management and purchasing data back to those Lansweeper records.

Setup and customization:

• Trigger: scheduled. Set the frequency and time to whatever suits your environment.
• Connection: uses the shared Jamf Pro connection from Part two.
• No other configuration is required. The workflow creates its own custom fields on first run (see Part four).

Freshness check: the workflow uses the warranty date to decide whether a record needs updating. If the warranty date in Jamf already matches Lansweeper, it skips that device to avoid unnecessary writes. If the dates differ, or Lansweeper has no warranty date yet, it updates the record. A device with no warranty date in Jamf gets updated on every run. This is expected, so devices with incomplete Jamf data still get enriched.

Lansweeper fields updated: Model, System SKU, Barcode, Contact, Cost Centre, Order Number, Purchase Date, Warranty End Date, Vendor, Acquisition Type, Owner, Description (records the device's Apple hardware identity marker, or UDID), Comment (records which Flow Builder flow enriched the record), Jamf ID (custom field), Jamf URL (custom field).

Workflow 2: Enrich Apple Devices with Jamf Pro Details

Purpose: matches iPhones and iPads already in Lansweeper against Jamf Pro by device name, then writes Jamf's management and purchasing data back, including the serial number, which Lansweeper cannot capture for mobile devices on its own.

Setup and customization:

• Trigger: scheduled. Set the frequency and time to whatever suits your environment.
• Connection: uses the shared Jamf Pro connection from Part two.
• No other configuration is required.

Lansweeper discovers iPhones and iPads by device name rather than serial number or MAC address, because iOS randomizes the MAC address per network and mobile devices are not scanned directly. Make sure device names in Jamf Pro match what Lansweeper reports, or devices will not match.

Freshness check: works the same way as Workflow 1: the warranty date decides whether a record needs updating, and a device with no warranty date in Jamf gets updated on every run.

Lansweeper fields updated: Serial Number, Model, System SKU, MAC, Manufacturer, Contact, Cost Centre, Order Number, Purchase Date, Warranty End Date, Vendor, Acquisition Type, Owner, Description (UDID), Comment, Jamf ID (custom field), Jamf URL (custom field).

Workflow 3: Create Assets for Jamf Pro Enrolled Computers

Purpose: finds Mac computers enrolled in Jamf Pro with no matching Lansweeper record, and creates one. This catches off-network or remote Macs that Lansweeper has not discovered on its own.

Setup and customization:

• Trigger: scheduled. Set the frequency and time to whatever suits your environment.
• Mode: set to dryrun to log what the workflow would create without making changes, or import to commit. Always test in dry-run mode first and check the log before switching to import.
• Asset type and state: set to fixed values for your Lansweeper site when the flow was configured, rather than looked up automatically. If you copy this flow to a different site, reselect the correct type and state first.
• Run Workflow 1 first, so records it already enriches are correctly skipped here rather than duplicated.

Lansweeper fields written: Name, Serial Number, Manufacturer, Model, System SKU, MAC, IP Address, Barcode, Contact, Order Number, Purchase Date, Warranty End Date, Acquisition Type, Description (UDID), Comment (identifies the record as created by this flow, used by Workflow 5 to find it again), Jamf ID (custom field), Jamf URL (custom field).

Workflow 4: Create Assets for Jamf Pro Enrolled Mobile Devices

Purpose: finds iPhones and iPads enrolled in Jamf Pro with no matching Lansweeper record, and creates one. It only creates assets for iPhones and iPads. Other Jamf-enrolled device types, such as Apple TV or Apple Watch, are skipped.

Setup and customization:

• Trigger: scheduled. Set the frequency and time to whatever suits your environment.
• Mode: set to dryrun or import, same as Workflow 3. Always test in dry-run mode first.
• Prerequisite: the "iPad" and "iPhone" asset types must already exist in Lansweeper before you run this workflow. It looks them up by name and does not create them for you.
• Run Workflow 2 first, so devices it already enriches are correctly skipped here rather than duplicated.

Lansweeper fields written: Name, Serial Number, Manufacturer, Model, System SKU, MAC, Contact, Order Number, Purchase Date, Warranty End Date, Acquisition Type, Description (UDID), Comment (identifies the record as created by this flow, used by Workflow 6 to find it again), Jamf ID (custom field), Jamf URL (custom field).

Workflow 5: Cleanup Computer Assets Imported From Jamf Pro

Purpose: removes Mac asset records that Workflow 3 created. Use this as a safe rollback if you need to reset and start again.

Setup and customization:

• Trigger: Universal Webhook. Call the webhook URL to run it manually.
• Delete flag: ships with deleteAssets set to false (dry run). In dry run mode it logs each asset it would delete but takes no action. Set deleteAssets to true to commit deletions.

The workflow only deletes records it can confirm Workflow 3 created, so it never removes a Mac that Lansweeper discovered independently.

Workflow 6: Cleanup Mobile Device Assets Imported From Jamf Pro

Purpose: removes iPhone and iPad asset records that Workflow 4 created. Works the same way as Workflow 5, for mobile devices.

Setup and customization:

• Trigger: Universal Webhook. Call the webhook URL to run it manually.
• Delete flag: ships with deleteAssets set to false (dry run). Set to true to commit deletions.

Part four: Custom fields created by these workflows

All 6 workflows share 2 custom fields. Workflows 1 and 2 both check for these fields on first run and create them if they do not exist. You do not need any manual setup.

Checking results in Lansweeper

After running the enrichment workflows, open any matched Mac or mobile device record in Lansweeper. The Jamf fields appear under the asset details, and the Jamf URL custom field links directly back to the Jamf Pro record.

After running the creation workflows (in import mode), new asset records appear in Lansweeper. Each carries a comment identifying it as created by Flow Builder.

If fields are not populating, check:

• The Flow Builder connection is using the correct Jamf Pro host URL and client credentials.
• The API role has both Read Computers and Read Mobile Devices privileges.
• The API client is enabled in Jamf Pro (disabled clients return authentication errors silently).

Summary

1. Create an API role in Jamf Pro with Read Computers and Read Mobile Devices privileges.
2. Create an API client, generate a client secret, and copy both the client ID and secret.
3. Create a Jamf Client Credentials connection in Flow Builder using your Jamf Pro URL and the client credentials.
4. Run Workflow 1 to enrich Mac computers already in Lansweeper.
5. Run Workflow 2 to enrich mobile devices. This also writes serial numbers back, which the creation workflows depend on.
6. Run Workflow 3 in dry-run mode first, verify the output, then switch to import mode to create missing Mac records.
7. Run Workflow 4 in dry-run mode first, verify, then switch to import mode for mobile devices.
8. Use Workflows 5 and 6 if you need to roll back any created records.

The result is a Lansweeper asset estate where every Apple device, whether discovered by network scan or enrolled in Jamf Pro, carries consistent management data, warranty information, and a direct link back to its Jamf record.