Overview

The NinjaOne integration connects your NinjaOne RMM instance with Core, automatically syncing managed devices into your asset inventory. Devices are matched to existing customers via organization mapping, giving you a unified view of all client IT assets alongside your tickets, contracts, and contacts.

What Gets Synced

When you sync devices from NinjaOne, Core imports:

Devices are also linked to customers automatically when NinjaOne organizations match existing Core customers by name.

Prerequisites

• A NinjaOne account with API access
• Admin permissions in your NinjaOne instance
• The integrations:manage permission in Core

Setting Up

1. Create an API Client in NinjaOne

1. In NinjaOne, go to Administration > Apps > API
2. Add a new client application
3. Select API Services (machine-to-machine) as the application platform

2. Configure the Client App

Set the following in your NinjaOne API client:

Redirect URI:

https://your-core-domain.com/api/integrations/ninja/callback

Scopes:

• Monitoring (required)

Allowed grant types:

• Authorization code
• Client credentials
• Refresh token

3. Add the Integration in Core

1. Go to Settings > Integrations
2. Add a new NinjaOne integration
3. Enter your Client ID and Client Secret from NinjaOne
4. Select your NinjaOne region (US, EU, Oceania, Canada, or US2)
5. Optional: enter your Dashboard Link Domain if your team uses a branded NinjaOne portal domain. Core uses this domain when opening device dashboard links from tickets.

4. Authorize the Connection

1. Navigate to Settings > Integrations > NinjaOne
2. Click Connect NinjaOne
3. You'll be redirected to NinjaOne to authorize
4. After approval, you're returned to Core with an active connection

Regional Instances

NinjaOne operates in multiple regions. Select the correct one during setup:

Syncing Devices

Manual Sync

Once connected, sync devices on demand:

1. Go to Settings > Integrations > NinjaOne
2. Click Sync Devices
3. Core fetches all devices from NinjaOne and creates or updates corresponding assets

You can also run Ninja sync from Settings > Integrations using Sync Now on the Ninja integration card.

The sync results show:

• Number of devices found
• Assets created (new devices)
• Assets updated (existing devices)
• Organizations matched to customers
• Unmatched organizations

Scheduled Sync

Set up automatic syncing so your device inventory stays current:

1. Go to Settings > Integrations > NinjaOne
2. In the Device Sync card, use the frequency selector to choose Hourly, Daily, or Weekly
3. The next scheduled sync time is displayed below the selector

Select Manual to disable automatic syncing and only sync on demand. The schedule applies to organization, contact, and device syncing.

Organization-to-Customer Mapping

During sync, Core automatically maps NinjaOne organizations to your existing customers using saved mappings and name matching. You can review and map organizations in two ways:

Quick mapping panel — Click Map Organizations on the Device Sync card to open a side panel for quick edits.

Full mapping review page — Go to the Organization Mapping card and click Review Mappings for a dedicated page view. This is also the page linked from inbox notifications.

Both views show all NinjaOne organizations with their mapping status:

• Mapped (green) — already linked to a customer
• Auto-matched (amber) — Core found a likely customer match by name; review and confirm
• Unmatched (red) — no match found; select a customer from the picker
• Stale (yellow) — the mapped customer was deleted; reassign

Use the customer picker on each row to assign or change the mapping, then click Save Mappings. When all organizations are mapped, the review page shows a completion state.

Mapping Review Notifications

After each sync, Core checks for unmapped organizations and unassigned device contacts. If any need attention, owners and admins receive an inbox notification with a direct link to the relevant review page:

• Organization mapping — Links to the organization mapping review page
• Contact assignment — Links to the contact association page

Notifications are deduplicated so you only receive one per day for each type.

Device Categories

NinjaOne device types are automatically categorized:

Viewing Synced Assets

After syncing, NinjaOne devices appear in your Assets page alongside manually created assets. Each synced asset includes:

• Device name, manufacturer, model, and serial number
• Online/offline status from NinjaOne
• Customer association (when organization is mapped)
• Category based on device type

Device Reports

Generate reports on your NinjaOne device fleet from Reports > Device Reports:

• Devices by Company — Total devices, online/offline counts, and device types grouped by customer
• Device Age — Age distribution across bands (0-1yr, 1-2yr, 2-3yr, 3-5yr, 5+yr) with drill-down to individual devices
• Warranty Status — Categorizes devices as Active, Expiring Soon (90 days), Expired, or No Warranty

All reports support filtering by customer, device type, and online status.

EOL Replacement Recommendations

Plan hardware refreshes with configurable replacement policies:

1. Go to Settings > Integrations > NinjaOne > Manage Replacement Policies
2. Set maximum device age and warning thresholds per device category (e.g., Workstations: 48 months, Servers: 60 months)
3. Create global defaults or per-customer overrides
4. View recommendations at Assets > EOL Recommendations to see which devices are overdue, approaching end-of-life, or compliant

Bulk Device Assignment

Assign NinjaOne device assets to contacts in bulk:

1. Navigate to a company's Assets page
2. If unassigned NinjaOne devices exist, click Assign Devices
3. Select devices and choose a contact for each, or use "Assign all selected to" for a single contact
4. Confirm to create the assignments

Bulk Contact Association

Automatically match NinjaOne device users to contacts using username patterns:

1. Go to Settings > Integrations > NinjaOne > Bulk Contact Association
2. Core extracts the last logged-in user from each device and matches usernames to contact emails
3. High-confidence matches (exact email, username prefix, full name, and username formats like firstnameLastname or lastnamefirstname) are shown with a confidence percentage and start pre-selected — their checkbox is already ticked, ready to apply. If the device name also contains the same person's name, Core treats that as the strongest match.
4. Each suggestion shows the contact name and email; use the dropdown to pick a different suggestion or choose No contact — skip for now to leave a device unassociated
5. Use the override (contact picker) column to search and assign a contact not in the suggestions; the search filters as you type. Choosing a contact for any device automatically queues that row, so the Apply Selected button appears without a separate step
6. Review, then use the bottom action bar to click Apply selected for the rows you've queued on this page, or Auto-apply 80%+ (all pages) to apply every strong match across all pages at once

NinjaOne Devices on Tickets

When a ticket has a contact with NinjaOne device assets assigned, the ticket sidebar shows a NinjaOne Devices card listing each device with:

• Online/offline status indicator
• Device name and type
• One-click link to open the device dashboard in NinjaOne

Reconnecting

If your OAuth token expires or you need to re-authorize:

1. Go to Settings > Integrations > NinjaOne
2. Click Reconnect
3. Complete the OAuth flow again

Troubleshooting

"NinjaOne not connected"

Ensure you've completed the full OAuth flow:

1. Added the integration with Client ID and Secret
2. Clicked Connect NinjaOne and authorized in NinjaOne

Devices not appearing after sync

Check:

1. Your NinjaOne API client has the Monitoring scope enabled
2. The connection shows as Connected with a green badge
3. Devices exist in your NinjaOne instance

Organizations not matching customers

Click Map Organizations to manually assign NinjaOne organizations to Core customers. The mapping panel uses fuzzy name matching to suggest likely matches, and you can override any suggestion with the customer picker. Previously, only exact name matches were detected automatically.

See also

• Integrations Overview
• IT Asset Management
• Asset Assignment & Lifecycle

Overview

The NinjaOne integration connects your NinjaOne RMM instance with Core, automatically syncing managed devices into your asset inventory. Devices are matched to existing customers via organization mapping, giving you a unified view of all client IT assets alongside your tickets, contracts, and contacts.

What Gets Synced

When you sync devices from NinjaOne, Core imports:

Devices are also linked to customers automatically when NinjaOne organizations match existing Core customers by name.

Prerequisites

• A NinjaOne account with API access
• Admin permissions in your NinjaOne instance
• The integrations:manage permission in Core

Setting Up

1. Create an API Client in NinjaOne

1. In NinjaOne, go to Administration > Apps > API
2. Add a new client application
3. Select API Services (machine-to-machine) as the application platform

2. Configure the Client App

Set the following in your NinjaOne API client:

Redirect URI:

https://your-core-domain.com/api/integrations/ninja/callback

Scopes:

• Monitoring (required)

Allowed grant types:

• Authorization code
• Client credentials
• Refresh token

3. Add the Integration in Core

1. Go to Settings > Integrations
2. Add a new NinjaOne integration
3. Enter your Client ID and Client Secret from NinjaOne
4. Select your NinjaOne region (US, EU, Oceania, Canada, or US2)
5. Optional: enter your Dashboard Link Domain if your team uses a branded NinjaOne portal domain. Core uses this domain when opening device dashboard links from tickets.

4. Authorize the Connection

1. Navigate to Settings > Integrations > NinjaOne
2. Click Connect NinjaOne
3. You'll be redirected to NinjaOne to authorize
4. After approval, you're returned to Core with an active connection

Regional Instances

NinjaOne operates in multiple regions. Select the correct one during setup:

Syncing Devices

Manual Sync

Once connected, sync devices on demand:

1. Go to Settings > Integrations > NinjaOne
2. Click Sync Devices
3. Core fetches all devices from NinjaOne and creates or updates corresponding assets

You can also run Ninja sync from Settings > Integrations using Sync Now on the Ninja integration card.

The sync results show:

• Number of devices found
• Assets created (new devices)
• Assets updated (existing devices)
• Organizations matched to customers
• Unmatched organizations

Scheduled Sync

Set up automatic syncing so your device inventory stays current:

1. Go to Settings > Integrations > NinjaOne
2. In the Device Sync card, use the frequency selector to choose Hourly, Daily, or Weekly
3. The next scheduled sync time is displayed below the selector

Select Manual to disable automatic syncing and only sync on demand. The schedule applies to organization, contact, and device syncing.

Organization-to-Customer Mapping

During sync, Core automatically maps NinjaOne organizations to your existing customers using saved mappings and name matching. You can review and map organizations in two ways:

Quick mapping panel — Click Map Organizations on the Device Sync card to open a side panel for quick edits.

Full mapping review page — Go to the Organization Mapping card and click Review Mappings for a dedicated page view. This is also the page linked from inbox notifications.

Both views show all NinjaOne organizations with their mapping status:

• Mapped (green) — already linked to a customer
• Auto-matched (amber) — Core found a likely customer match by name; review and confirm
• Unmatched (red) — no match found; select a customer from the picker
• Stale (yellow) — the mapped customer was deleted; reassign

Use the customer picker on each row to assign or change the mapping, then click Save Mappings. When all organizations are mapped, the review page shows a completion state.

Mapping Review Notifications

After each sync, Core checks for unmapped organizations and unassigned device contacts. If any need attention, owners and admins receive an inbox notification with a direct link to the relevant review page:

• Organization mapping — Links to the organization mapping review page
• Contact assignment — Links to the contact association page

Notifications are deduplicated so you only receive one per day for each type.

Device Categories

NinjaOne device types are automatically categorized:

Viewing Synced Assets

After syncing, NinjaOne devices appear in your Assets page alongside manually created assets. Each synced asset includes:

• Device name, manufacturer, model, and serial number
• Online/offline status from NinjaOne
• Customer association (when organization is mapped)
• Category based on device type

Device Reports

Generate reports on your NinjaOne device fleet from Reports > Device Reports:

• Devices by Company — Total devices, online/offline counts, and device types grouped by customer
• Device Age — Age distribution across bands (0-1yr, 1-2yr, 2-3yr, 3-5yr, 5+yr) with drill-down to individual devices
• Warranty Status — Categorizes devices as Active, Expiring Soon (90 days), Expired, or No Warranty

All reports support filtering by customer, device type, and online status.

EOL Replacement Recommendations

Plan hardware refreshes with configurable replacement policies:

1. Go to Settings > Integrations > NinjaOne > Manage Replacement Policies
2. Set maximum device age and warning thresholds per device category (e.g., Workstations: 48 months, Servers: 60 months)
3. Create global defaults or per-customer overrides
4. View recommendations at Assets > EOL Recommendations to see which devices are overdue, approaching end-of-life, or compliant

Bulk Device Assignment

Assign NinjaOne device assets to contacts in bulk:

1. Navigate to a company's Assets page
2. If unassigned NinjaOne devices exist, click Assign Devices
3. Select devices and choose a contact for each, or use "Assign all selected to" for a single contact
4. Confirm to create the assignments

Bulk Contact Association

Automatically match NinjaOne device users to contacts using username patterns:

1. Go to Settings > Integrations > NinjaOne > Bulk Contact Association
2. Core extracts the last logged-in user from each device and matches usernames to contact emails
3. High-confidence matches (exact email, username prefix, full name, and username formats like firstnameLastname or lastnamefirstname) are shown with a confidence percentage and start pre-selected — their checkbox is already ticked, ready to apply. If the device name also contains the same person's name, Core treats that as the strongest match.
4. Each suggestion shows the contact name and email; use the dropdown to pick a different suggestion or choose No contact — skip for now to leave a device unassociated
5. Use the override (contact picker) column to search and assign a contact not in the suggestions; the search filters as you type. Choosing a contact for any device automatically queues that row, so the Apply Selected button appears without a separate step
6. Review, then use the bottom action bar to click Apply selected for the rows you've queued on this page, or Auto-apply 80%+ (all pages) to apply every strong match across all pages at once

NinjaOne Devices on Tickets

When a ticket has a contact with NinjaOne device assets assigned, the ticket sidebar shows a NinjaOne Devices card listing each device with:

• Online/offline status indicator
• Device name and type
• One-click link to open the device dashboard in NinjaOne

Reconnecting

If your OAuth token expires or you need to re-authorize:

1. Go to Settings > Integrations > NinjaOne
2. Click Reconnect
3. Complete the OAuth flow again

Troubleshooting

"NinjaOne not connected"

Ensure you've completed the full OAuth flow:

1. Added the integration with Client ID and Secret
2. Clicked Connect NinjaOne and authorized in NinjaOne

Devices not appearing after sync

Check:

1. Your NinjaOne API client has the Monitoring scope enabled
2. The connection shows as Connected with a green badge
3. Devices exist in your NinjaOne instance

Organizations not matching customers

Click Map Organizations to manually assign NinjaOne organizations to Core customers. The mapping panel uses fuzzy name matching to suggest likely matches, and you can override any suggestion with the customer picker. Previously, only exact name matches were detected automatically.

See also

• Integrations Overview
• IT Asset Management
• Asset Assignment & Lifecycle