Creating an extended integration for MSP NinjaOne assets

Sync Oomnitza with NinjaOne to gain visibility of MSP (Managed Service Provider) asset and software data. 

Before you start

To easily find the records that are uploaded to Oomnitza, it's best practice to create a dedicated user account for each integration. This will make it easier for you to retrieve the records that are uploaded to Oomnitza from the vendor application. 

Creating integration users 

Information required to create the integration

To add the integration, you must enter: To add the integration, you must enter, your NinjaOne URL. The format of the URL is https://<subdomain>.rmmservice.com.

To add credentials to Oomnitza, you must enter:

• Your client ID and secret. 
• The API scope or scopes. Make sure Refresh Token and Authorization Code are selected as the grant types. 
• Your NinjaOne subdomain.

When you create the application in NinjaOne, make sure Refresh Token and Authorization Code are selected as the grant types and all the scopes are selected. See API OAuth Token Configuration.

When prompted, enter this redirect URL: https://generic-oauth2-proxy.oomnitza.com/oauth2/redirect.

Adding credentials

Make life easier and add your credentials to Oomnitza before you create the integration.  

1. In Oomnitza, click Configuration > Security > Credentials.
2. Click Add new credential (+).
3. Search for the integration, and then click the forward arrow > to select the integration.
4. Enter your client credentials and any other additional information.
5. Click Authenticate. You are prompted to log in to authorize your request.
6. Click CREATE.

Enter scopes separated by spaces such as monitoring management.

Adding the integration

1. In Oomnitza, click Configuration> Integrations> Overview.
2. Click Block view
3. Scroll down to the Extended section for asset integrations.
4. Click NEW INTEGRATION.
5. Select the integration in the sidebar.
6. Click ADD.

Integration details overview

More information is provided about the following fields to help you complete the integration:

Software data

Depending on the asset integration, an option might be available to ingest desktop software information such as the name and version of the software installed on an asset. To view the software information in Oomnitza, you must have the software module. 

Installation types

• Cloud. Store credentials in the Oomnitza cloud.
• Local. Store credentials locally. If you want to sync Oomnitza with vendor applications that require AWS or OAUTH authentication, select cloud as the type of installation. Local installations don't support AWS and OAuth authentication. 

Integration preferences

• Create & Update. Add and update records.
• Create only. Add records.
• Update only. Update records.

Integration details

To review or update the integrations details, click Edit .

When you edit the Integration details section, you can select the name or names of integration contacts.  Integration contacts will receive an in-app notification and an email, when the integration fails, when the integration fails to complete within 24 hours, or when the scheduled integration fails to run.

1. Update the integration name.
2. Select an installation type.
3. For integration preferences, select an option.
4. Enter the name of the integration user.  

Credential details

If you selected Cloud as the installation type, choose one of the following options:

• Select the credentials that were created for the integration.
• Edit the credentials that were created for the integration.
• Create new credentials

Scheduling the integration

By default, data is synced once every day. Change the interval or the time so that the data is streamed when your system isn't busy.

1. Click Edit .
2. Make and save your changes.

Mapping fields to Oomnitza

To map the fields to Oomnitza, click Edit .

  Select Edit integration to add rules for syncing data. Filtering integration results.  

Click SMART MAPPING.

You can add new fields to your integration by selecting Add new field   on the mapping page. 
Creating custom API fields. 

Mappable fields

Approval Status
Connector Sync Time
Created
Device Name
Device Type
Dns Name
Id
Ip Addresses List
Last Contact
Last Logged In User
Last Update
Location Id
Mac Addresses List
Memory Capacity
Node Class
Node Role Id
Offline
Organization Id
Os Architecture
Os Build Number
Os Language
Os Last Boot Time
Os Locale
Os Manufacturer
Os Name
Os Needs Reboot
Os Service Pack Major Version
Os Service Pack Minor Version
Processors Architecture
Processors Clock Speed
Processors Max Clock Speed
Processors Name
Processors Num Cores
Processors Num Logical Cores
Public IP
Role Policy Id
System Bios Serial Number
System Chassis Type
System Domain
System Domain Role
System Manufacturer
System Model
System Name
System Number Of Processors
System Serial Number
System Total Physical Memory
System Virtual Machine
Tags List
Volumes Auto Mount
Volumes Capacity
Volumes Compressed
Volumes Device Type
Volumes File System
Volumes Free Space
Volumes Label
Volumes Name
Volumes Serial Number

Drag and drop

You can map additional fields to Oomnitza.

1. Drag and drop the fields onto the Add new Oomnitza field area in the Oomnitza column.
2. Rename the field.
3. Make your changes.
4. Save your changes.

Selecting sync keys

You must select at least one field as the sync key field. To ensure that the sync runs successfully, the field must contain unique values such as the serial number of an asset record or the email address of a user record. Records that do not contain a value for the sync key are skipped.   

See Configuring multiple sync keys.