Current + NinjaOne integration

NinjaOne is where a lot of MSPs keep the whole managed estate: Windows and Mac workstations, Linux and virtual servers, and the switches and network gear alongside them. Current's NinjaOne integration is a view-only feed into the SBR/QBR module and the company alert band. It reads what NinjaOne already knows and never writes back.

What the integration does

Current authenticates to NinjaOne with a machine-to-machine API application scoped to monitoring, walks your organizations and devices every six hours, and stages the result as evidence for AI-assisted Strategic Business Reviews. Instead of exporting a device list the week of the review, the fleet numbers are already sitting on the company record when you open it.

What data flows

• Organizations — the NinjaOne customer roster, matched to your Current companies so every signal below lands on the right record.
• Device inventory — Windows, Mac, and Linux endpoints and servers, plus the network devices NinjaOne monitors, with operating system, serial, location, and online or last-contact time.
• Patch posture — pending and failed operating-system patches per device, and whether the device counts as patch-compliant.
• Antivirus status — the product state NinjaOne reports per device, and whether that state is healthy.
• Active alerts — the conditions firing right now, with severity, priority, and when NinjaOne raised them.

The feed is one-way. Current does not run scripts, send device commands, deploy software, or edit policies in NinjaOne. Those endpoints are not in the connector's code, so they cannot be reached by a bug either. NinjaOne stays the source of truth for management; Current uses the evidence.

Unknown reads as unknown

A device NinjaOne has no patch or antivirus report for shows as unknown in Current, not as compliant. That distinction matters in a review: a fleet number built by treating silence as a pass is a number you cannot defend when a partner asks which machines it covers. If a whole report comes back empty, every device on it reads unknown rather than the fleet appearing to pass.

Alerts that clear themselves

Current mirrors the alert set that is active at each sync, so a condition that resets in NinjaOne leaves Current on the next run instead of accumulating as history. The company alert band reads from that live set: it turns critical on the first critical NinjaOne alert and warns once critical and major alerts together reach three, then clears on its own when the conditions reset. Account managers see open problems, not a scrolling log of everything that ever fired.

Matching organizations to companies

Each NinjaOne organization is one end-customer. Current links organizations to companies by normalized name — punctuation and Inc/LLC/Ltd-style suffixes stripped — and only when exactly one company matches. Where two companies could both be the answer, the organization stays on an unmapped list for a person to decide rather than being paired on a guess. A mapping set by hand is never overwritten by a later automatic match, and mapping an organization attaches its devices and alerts immediately instead of waiting for the next scheduled sync.

Where the data appears

• In Strategic Business Reviews, in the fleet and network chapter alongside your other monitoring feeds.
• On the company record, where posture shows device counts by class with patch and antivirus health.
• In dashboard device metrics, including endpoint counts and device-compliance percentages.
• In the company alert band, as an active-alerts entry that reflects what is firing now.

Why it matters

The fleet section is where most business reviews get vague, because the numbers live in the RMM and the review lives somewhere else. An MSP running NinjaOne for a partner like Northwind Traders can open the account and see the managed device count, how many machines are behind on patches, which ones have antivirus in a state worth talking about, and what is alerting today — without anyone assembling an export first. The review becomes a conversation about what the data says rather than about where the data came from.