Onward pricing update, effective January 1, 2027

NinjaOne to Assets: Import Device Details from NinjaOne to JSM Assets

Buzz

OnLink now imports device details from NinjaOne straight into Atlassian Assets, so your CMDB reflects every managed endpoint without manuak exports or custom coding.

Setup takes three steps: connect to the NinjaOne API, pull your devices, and map the fields into Assets.

Step 1: Connect OnLink to the NinjaOne API

OnLink connects to the NinjaOne Public API with OAuth client credentials. This is a machine-to-machine flow, so no user has to sign in.

In NinjaOne, go to Administration > Apps > API and add a client app.
Choose API Services (machine-to-machine).
Set the scope to Monitoring and the grant type to Client Credentials.
Copy the Client ID and Client Secret. The secret is shown only once.
In OnLink, create a new NinjaOne connection and use the API link to parse the connection details.
Select OAuth client credentials.
Set Token URL to https://app.ninjarmm.com/ws/oauth/token.
Enter the Client ID and Client Secret.

The read-only Monitoring scope is all OnLink needs to import device data. See NinjaOne’s Client Credentials Flow.

Step 2: Get devices from NinjaOne

In the same connection, set up a GET request for your devices:

Set Method to GET.
Set URL to the NinjaOne getDevices endpoint.
Leave Response data path empty.
Keep the other settings at their defaults unless you add query parameters.

GET https://app.ninjarmm.com/v2/devices

The NinjaOne API paginates results, so turn on pagination in OnLink to pull your whole fleet. To limit what comes back, add a device filter. For example, df=status = APPROVED returns approved devices only.

Save the connection, then run it to fetch sample JSON. The sample confirms the endpoint works and shows the field names you’ll map next.

Step 3: Map NinjaOne devices to Assets in OnLink

Create the Assets import by following the JSM Assets Data Synchronization guide. Then map NinjaOne fields to Assets attributes using key: and map: statements. The key: should be a stable, unique value, so OnLink updates existing objects instead of creating duplicates.

OnLink mapping	What it does
`key:id=Device ID`	Uses the NinjaOne device `id` as the unique key to match and update Assets objects
`map:hostname=Hostname`	Stores the device hostname
`map:uuid=UUID`	Stores the device UUID for extra identification
`map:platform=Platform`	Records the OS or platform reported for the device
`map:hardware_model=Hardware Model`	Stores the hardware model
`map:display_name=Display Name`	Stores the device name shown in NinjaOne
`map:primary_ip=Primary IP`	Stores the device’s primary IP address

These are examples. You can map any field in the response, as long as the matching Assets attribute exists. Use Get Data to preview the records and check that attribute names and case match. Once everything looks right, run the import and set a schedule. From then on, OnLink keeps Assets in sync as devices are added, changed, or retired in NinjaOne.

Try OnLink for NinjaOne to Assets

Your agents shouldn’t need a second console to know which laptop a user has, what OS it runs, or when it last checked in. With NinjaOne data in Assets, they can:

Link incidents and requests to the exact device affected
Tie each device to its owner for faster onboarding and offboarding
Spot stale or offline devices before they become audit findings
Report on your full fleet next to the rest of your CMDB

OnLink is Cloud Fortified and connects 100+ sources, including NinjaOne, Intune, Jamf Pro, and your HR systems, in one app.

Start your free trial of OnLink on the Atlassian Marketplace → OnLink

FAQs NinjaOne to Atlassian Assets

What NinjaOne permissions does OnLink need?

Only the read-only Monitoring scope, with the Client Credentials grant type. OnLink reads device data and never changes anything in NinjaOne.

My NinjaOne tenant isn’t on app.ninjarmm.com. Will it still work?

Yes. Use your own instance host, such as eu.ninjarmm.com or ca.ninjarmm.com, in both the Token URL and the request URL.

Can I import only some devices?

Yes. Add a NinjaOne device filter (df) to the request URL. For example, df=status = APPROVED returns approved devices only.

How does OnLink avoid creating duplicate assets?

The key: mapping uses the NinjaOne device id to match records. If an object with that key already exists, OnLink updates it instead of creating a new one.

Can I map fields that aren’t in the example table?

Yes. You can map any field returned in the response, as long as a matching attribute exists on your Assets object type.

How do I keep Assets up to date?

Set a schedule on the import in OnLink. Each run picks up devices that were added or changed in NinjaOne since the last sync.

What if I lose the Client Secret?

NinjaOne shows the secret only once. Regenerate it under Administration > Apps > API, then update the OnLink connection.

Can I combine NinjaOne with other device and HR sources?

Yes. OnLink connects 100+ sources in one app, including Intune, Jamf Pro, and HR systems. That lets you link NinjaOne devices to the people who use them.