Connect NinjaOne
Connect NinjaOne to bring the Windows, Linux and macOS devices of your organizations into Excubius, with their last contact, their pending patches and NinjaOne's own alerts. This guide shows the least-privilege API client on the NinjaOne side, how to add the source and how to receive alerts by webhook.
Before you begin
- You need the Entity admin role on the entity the devices belong to.
- In NinjaOne, you can add an API client app under Administration › Apps › API.
- The feature
sources.ninjaoneis on. See Sources.
What Excubius reads
NinjaOne is read through its public API v2, with GET requests only, plus the request for an OAuth token.
| Phase | What | Default interval |
|---|---|---|
| Inventory | Detailed devices and the organization names. Windows, Linux and macOS devices become hosts with their operating system, last contact, offline flag and their organization as the tag client. Other node classes, such as network devices, cloud monitors and hypervisors, are counted and skipped | 15 minutes |
| Metrics | Minutes since the last contact (warning after 15, critical after 60) and, unless you switch it off, pending operating system and software patches that are approved and not installed | 15 minutes |
| Alerts | Active alerts, one alert each, with the NinjaOne condition as the rule | 5 minutes in Polling; reconciliation every 15 minutes in Hybrid |
Prepare NinjaOne
- Open Administration › Apps › API › Client App IDs and select Add.
- Choose the application platform API Services (machine-to-machine), the scope Monitoring only and the grant type Client Credentials.
- Save, then copy the client ID and the client secret.
- Note the region of your instance:
app.ninjarmm.com(United States),eu.,oc.orca.ninjarmm.com.
Give the client the Monitoring scope only. The Management and Control scopes can change devices and run scripts, and Excubius never needs them.
Add the source
- Open Settings › Sources, select Add a source and choose NinjaOne.
- Under General, enter a Name and choose the Entity.
- Under Connection, choose the Region and enter the Client ID and the Client secret.
- Optionally, list the Organizations to read, as organization IDs separated by commas. Leave it empty to read every organization the client can see.
- Keep Pending patches to bring in approved operating system and software patches that are not installed yet.
- Under Ingest mode, choose Hybrid (recommended), or Polling when NinjaOne cannot reach the Excubius server.
- Optionally, under Webhook, enter a Webhook secret.
- Select Create source and copy the webhook URL. It is shown only once.
Receive alerts by webhook
NinjaOne sends webhooks to a URL registered through its API (PUT /v2/webhook). An administrator does this once, with an API app allowed to manage NinjaOne, never with the read-only client you gave Excubius.
- Register the URL Excubius showed.
- If you set a webhook secret, add the header
X-Custom-Webhook-Secret: <secret>. NinjaOne acceptsAuthorizationandx-custom-*headers.
Condition activities TRIGGERED and RESET open and close alerts in Excubius; other activities are ignored.
Test and sync
- On the source page, select Test. Each read is listed with its result: credentials, organizations, devices, alerts and patches.
- Select Sync now to bring devices, metrics and alerts in without waiting.
Devices appear as Windows, Linux and macOS hosts, matched with the same servers from other sources and tagged with their organization. The NinjaOne checks and the pending patches check appear on them, and NinjaOne alerts appear in the Alert inbox.