OnLink · ServiceNow CMDB
OnLink pulls records from any ServiceNow CMDB table straight into Assets, with no middleware and no CSV exports.
Buzz
Keep ServiceNow as a source of truth for some records while JSM agents see them in Assets. Pull computers, servers, virtual machines, or hardware assets on a schedule. Agents can then link those objects to requests, incidents, and changes without switching tools.
Moving from ServiceNow to Jira Service Management? Your CMDB is usually the hardest part to move. OnLink reads CMDB tables such as cmdb_ci_computer and cmdb_ci_server and creates matching objects in Assets. Run it table by table, validate each one, and cut over when the data looks right.
OnLink supports both Basic Authentication and OAuth for the ServiceNow connection. Pick whichever your ServiceNow admin allows.
|
Method
|
What you provide in OnLink
|
|---|---|
|
Basic Auth |
ServiceNow username and password |
|
OAuth |
Client ID and client secret |
Setup takes three steps:
Access the integration account needs:
rest_api_explorer role, so the account can call the ServiceNow REST Table API.
Point OnLink at one ServiceNow table and it fetches every record in it. Configure the API call like this:
|
Setting
|
Value
|
|---|---|
|
Method
|
GET |
|
URL
|
https://{instance}.service-now.com/api/now/table/cmdb_ci_computer |
|
Response data path
|
result |
|
Query (optional)
|
sysparm_query=install_status=1 to import only installed CIs; sysparm_fields to trim the payload |
Swap the table name to import something else. Common choices:
cmdb_ci_computer
Laptops and desktops: name, serial number, OS, assigned user.
cmdb_ci_server
Physical and virtual servers with OS, IP and environment.
cmdb_ci_vm_instance
Virtual machines and their hosts.
alm_hardware
Hardware assets with model, cost center and lifecycle state.
Click Get Data to preview what comes back before you map anything. Each record arrives as JSON with fields like sys_id, name, serial_number, and os.
Each ServiceNow field maps to a JSM Assets attribute with one line of config. A key: line tells OnLink which field uniquely identifies a record, so repeat imports update existing objects. map: lines copy fields into attributes.
|
OnLink mapping
|
ServiceNow field
|
JSM Assets attribute
|
|---|---|---|
|
|
|
ID (unique match key) |
|
|
|
Name |
|
|
|
Serial Number |
|
|
|
OS Name |
|
|
|
Status |
|
|
|
Asset Tag |
|
|
|
OS Version |
|
|
|
IP Address |
|
|
|
Expiration Date |
If the goal is to leave ServiceNow, treat the CMDB as a sequence of small imports rather than one big bang. A typical four-week shape:
Start with the table agents ask about most, usually cmdb_ci_computer. Create the matching Assets object type with the attributes you will map.
Run Get Data, compare record counts with ServiceNow, spot-check serials and owners. Key on sys_id so re-runs update rather than duplicate.
Servers, VMs, hardware assets, users. Each table is its own data source and mapping, run on a schedule while ServiceNow stays the source of truth.
Point agents at Assets, freeze CMDB edits in ServiceNow, keep the scheduled sync running until the ServiceNow contract ends.
Try OnLink free on the Atlassian Marketplace. Planning a full ServiceNow-to-JSM migration? Book a 30-minute walkthrough and we will map your first table with you.
Any table the integration account can read through the Table API. Common ones are cmdb_ci_computer, cmdb_ci_server, cmdb_ci_vm_instance, and alm_hardware.
Read-only access to the tables or views you import, plus the rest_api_explorer role. No write access is required.
Both work. OAuth with a client ID and secret is usually preferred by security teams. Basic Auth is quicker for a proof of concept.
No. The key: mapping, typically sys_id, matches each record to its existing Assets object and updates it.
ServiceNow returns these as links and sys_ids. Resolve them to display values, such as a location name or user email, that match objects already in Assets.
The Assets import is read-only; the integration account only needs read access and the rest_api_explorer role. If you need to update ServiceNow from a Jira workflow, OnLink AI can call the ServiceNow REST API from Jira and JSM automations.
Yes. Any table the account can read works, including sys_user. Import users into a People object type and map assigned_to on your CI imports to link devices to their owners inside Assets.
Data Manager lists a ServiceNow adapter on JSM Premium and Enterprise. OnLink works on any JSM plan, imports any table rather than a fixed set, and lives in the same app as your HR, identity and device sources. Full comparison here.
ServiceNow data in Assets
Start a free trial of OnLink on the Atlassian Marketplace. Any ServiceNow CMDB table, plus 100+ other sources, in one app.
Try OnLink free on the Atlassian Marketplace or book a 30-minute walkthrough.
With ServiceNow data in Assets, your team can:
