This article details how to import Apple device inventory directly from Addigy into Assets using the OnLink.
Benefits of having Apple device data in Assets. Importing your Apple device data into Assets unlocks the following:
Centralized Inventory: View all your IT assets, including Apple devices, in one place.
Enhanced Context for Agents: Support agents can see the specific device details (model, serial number, online status) associated with a reporter immediately, leading to faster resolution times. Useful for any compliance validation, vulnerability audits and replacements.
Automated Asset Management: Reduce manual data entry and keep your asset database up-to-date automatically.
Common Use Cases
Incident Management: Automatically link a user's laptop to their support ticket to verify warranty status or specs.
Asset Lifecycle Tracking: Monitor device status (Online/Last Online) directly from Jira Service Management to identify unused or lost equipment.
Reporting & Compliance: Generate reports on device models and operational status within JSM for audits or refresh cycles.
Integrating to Addigy To start the integration, you first need to generate an API key within your Addigy account.
Get your Addigy API Key:
Log in to Addigy and navigate to Account > Integrations.
In the Addigy API section, select the V2 tab.
Click on New API Token.
Select the permissions you wish to allow. Note: Follow the principle of least privilege, granting only the permissions necessary for reading device data.
Copy the token and store it securely; you will not be able to view it again.
Addigy API Documentation Link.
Configure OnLink:
Go to OnLink (Manage your apps) > Connections.
Click Add System and select the "Other Data Sources" option.
API URL: Enter the URL in the following format: https://api.addigy.com/api/v2/o/<your org id>
API Key: Paste the Integration Key you generated in step 1.
Mapping Addigy Data to Assets Schema
To ensure data lands in the correct fields in Assets, you need to define a asset mapping configuration. View the Addigy API Documentation for the list of fields supported by Addigy - Link.
Example Configuration:
key:udid=id
map:device_name=Device Name
map:device_model_name=Model Name
map:serial_number=Serial Number
map:product_name=Product Name
map:identity_email=Email
map:identity_mobile_phone=Mobile
map:online=Online
map:last_online=Last Online
config:api=devices
Configuration Breakdown:
| Key or Map | Description |
key:udid=id |
Defines the unique identifier for the record. The keyword key tells OnLink to use udid to identify and update existing records. |
map:device_name=Device Name |
Maps the Addigy field device_name to the Assets attribute "Device Name". |
map:device_model_name=Model Name |
Maps the Addigy field device_model_name to the Assets attribute "Model Name". |
config:api=devices |
Specifies the configuration to pull the list of devices. Any fields from the Addigy V2 API can be included. |
FAQ
What is the correct API URL format? You must use the V2 API format: https://api.addigy.com/api/v2/o/<your org id>.
How do I test my mapping before going live? Use the manual trigger buttons in OnLink. First, click Get Data, verify the logs, and then click Import to push the data to Assets.
Can I map other fields not listed in the example? Yes, any fields available in the Addigy V2 API documentation can be mapped using the map:source_field=Target Attribute syntax.
Related Articles
Ready to import Apple device data into Assets? Try out OnLink today
Prabhu Palanisamy _Onward_
0 comments