NinjaOne

NinjaOne is the RMM source. Hal reads it so an alert that names a host arrives with the device already identified — what it is, whose it is, and whether it’s healthy. He never reasons about a hostname in isolation when the RMM can tell him the rest.

What Hal reads:

Managed device inventory — hostname, model, OS version, online or offline state, last contact
The organization structure that maps each device to a client
Patch status — pending, approved, and rejected OS and third-party patches
Installed software inventory
Antivirus product, version, real-time-protection state, and detected threats
Active RMM alerts and device activity

Access is strictly read-only. Hal uses NinjaOne’s monitoring-level access and never writes back, runs scripts, or changes a device.

How to connect

In the Hal portal, add a read-only NinjaOne API credential for your instance. Hal tests connectivity before the source goes live. Setup walkthroughs are in Getting Started.

The marketing overview — what NinjaOne gives Hal and why — is at /integrations/ninjaone/.

ConnectWise