RMM
NinjaOne
NinjaOne devices, software and pending patches, read through the API, without deploying another agent.
What the connector does
The connector reads the inventory NinjaOne already keeps: devices, installed software and pending or failed OS patches. Devices join your fleet, their software joins the monitored stack, and missing patches show on each machine's page. Optionally, TechWatchAlert writes the risk score into a custom field on each device.
What comes into TechWatchAlert
- Devices: OS, build, serial number, MAC and IP addresses, last user
- Installed software, matched with products known to CVEs
- Pending or failed OS patches, on each machine's page
- Optionally, in NinjaOne: one text field per device with the risk score, the number of critical flaws and a link to the machine
Setup
- In NinjaOne, create an “API Services (machine-to-machine)” API application with the “Client Credentials” grant and the “Monitoring” scope
- In TechWatchAlert, choose the region, enter the client ID and secret and, if needed, the organization to read
- For risk write-back, create a text-type device custom field and add the “Management” scope
In the same family
Datto RMMThe devices of your Datto RMM sites and their audited software, read through the API and monitored without another agent.View connector →N-able N-centralYour N-central customers' devices and their inventory, read through the API for CVE monitoring endpoint by endpoint.View connector →AteraYour Atera agents, their OS and their available patches, read through the API and matched with CVEs.View connector →
Connectors
Plug in your tools in minutes
Start with a repository, a fleet or a scan report: your first targeted alerts arrive with the first sync.
Free plan, no credit card · hosted in France

