Configure the connection to Kandji by going to OnLink (Manage your apps) - Connections. Then click on Add System and select “IdM/Device Assets Sources”. Here you can set the API URL and API Key from Kandji. See this document for reference: Kandji API Overview
Once connection is established, please review instructions here to get started with setting up an Assets import configuration. You can then access OnLink app from the “Manage your apps” menu to further configure and set the field level mapping. Here’s an example mapping configuration:
key:device_id=idmap:user.email=userIdmap:device_name=deviceNamemap:model=deviceModelmap:platform=operatingSystem
Here’s a breakdown of some of the mapping configuration items:
Key or Map | Description |
|---|---|
| The keyword “key” refers to using device_id as a unique identifier. This allows OnLink to update the record. “id” is a text attribute. |
| Maps user.email to userId text attribute |
Any other field returned by the API can be used in the mapping. See this link for a full list of available API fields: Kandji List Devices API
OnLink processes data in two steps - Get Data and Import Data. To manually test, you can click on Get Data first and then wait until you see “No more pending records. Data will be imported on next Import run.” message in Job Logs. Then, click on Import. Production runs are fully automated based on the schedule you choose.
