OnLink · Device management
OnLink imports device details from NinjaOne into Atlassian Assets, so your CMDB reflects every managed endpoint without manual exports or custom code.
Buzz
NinjaOne to Jira Service Management Assets with OnLink, in three steps.
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.
https://app.ninjarmm.com/ws/oauth/token.
The read-only Monitoring scope is all OnLink needs to import device data. See NinjaOne’s Client Credentials Flow.
In the same connection, set up a GET request for your devices:
|
Setting
|
Value
|
|---|---|
|
Method
|
GET |
|
URL
|
https://app.ninjarmm.com/v2/devices |
|
Response data path
|
leave empty (the response is a JSON array)
|
|
Pagination
|
On, so OnLink pulls the whole fleet
|
|
Optional filter
|
df=status = APPROVED to import approved devices only |
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.
A trimmed sample device looks like this:
[
{
"id": 118,
"organizationId": 2,
"locationId": 3,
"nodeClass": "WINDOWS_WORKSTATION",
"approvalStatus": "APPROVED",
"offline": false,
"displayName": "LAPTOP-7XK2",
"systemName": "LAPTOP-7XK2",
"dnsName": "laptop-7xk2.corp.example.com",
"created": 1727740800,
"lastContact": 1759449600,
"lastUpdate": 1759449600
}
]
eu.ninjarmm.com, ca.ninjarmm.com or oc.ninjarmm.com, use that host in both the token URL and the request URL.
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, so repeat syncs update instead of duplicate |
map:systemName=Hostname |
System name reported by the NinjaOne agent
|
map:displayName=Display Name |
The name shown in the NinjaOne console
|
map:dnsName=DNS Name |
Fully qualified DNS name
|
map:nodeClass=Device Class |
WINDOWS_WORKSTATION, MAC, LINUX_SERVER and so on
|
map:approvalStatus=Approval Status |
APPROVED or PENDING
|
map:offline=Offline |
Whether the agent is currently offline
|
map:lastContact=Last Contact |
Last check-in time; useful for stale-device filters
|
map:organizationId=Organization |
NinjaOne organization, handy for MSP-style multi-tenant setups
|
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.
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 on the Atlassian Marketplace.
Only the read-only Monitoring scope, with the Client Credentials grant type. OnLink reads device data and never changes anything in NinjaOne.
Yes. Use your own instance host, such as eu.ninjarmm.com or ca.ninjarmm.com, in both the Token URL and the request URL.
Yes. Add a NinjaOne device filter (df) to the request URL. For example, df=status = APPROVED returns approved devices only.
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.
Yes. You can map any field returned in the response, as long as a matching attribute exists on your Assets object type.
Set a schedule on the import in OnLink. Each run picks up devices that were added or changed in NinjaOne since the last sync.
NinjaOne shows the secret only once. Regenerate it under Administration > Apps > API, then update the OnLink connection.
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.
They complement each other. NinjaOne gives you RMM status, approval and last contact; Intune and Jamf Pro add compliance and configuration; Huntress adds security agents. OnLink imports all of them in one app, and keying on a shared value such as serial number or hostname merges them into one Assets object.
NinjaOne data in Assets
Start a free trial of OnLink on the Atlassian Marketplace. NinjaOne, Intune, Jamf Pro, Huntress and 100+ more in one app.
Your agents should not 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, your team can:
