RMM & Endpoint

NinjaOne

Monitor and manage your NinjaOne fleet - device inventory, patch and antivirus status, alerts, and on-demand actions.

Dex connects to NinjaOne (NinjaRMM) through the Public API v2 so admins can run the endpoint fleet conversationally - inventory organizations and devices, check OS-patch and antivirus compliance, triage active monitoring alerts, and take on-demand actions like running an Automation Library script, rebooting a device, or opening a maintenance window. Employees can check their own device's status, patches, software, and alerts through Dex Go. Available as an MSP global app: one set of API client credentials is shared, and each Dex tenant is confined to its NinjaOne Organization.

Book a Demo

What Dex does with NinjaOne

Dex handles both admin workflows and employee self-service — all policy-guardrailed and audit-logged.

For admins (CoAdmin)

Inventory organizations, locations, and devices - search by organization, node class, or online/offline state
Check per-device OS-patch status and install history, plus account-wide patch, antivirus, and device-health rollups
Triage active monitoring alerts by severity across the account or per device
Review per-device software inventory
Run Automation Library scripts and built-in actions on a device - with approval
Reboot devices (graceful or forced) and set maintenance windows to suppress alerts during work - with approval
Deploy as an MSP global app - one API client, each customer confined to its NinjaOne Organization

For employees (self-service)

Check whether your own device is online and when it last checked in
See your device's OS-patch status and recent update history
Review what software is installed on your machine
See active alerts on your device
Run an approved diagnostic, reboot, or maintenance window on your own device

Just ask Dex

Your team types a request in plain language. Dex investigates, plans, and executes — with the right guardrails.

Admin prompts

>Which Windows servers in NinjaOne are offline right now?
>Show me the critical alerts across all organizations
>What's the patch compliance picture for Contoso - any devices with failed patches?
>Reboot DESK-PARIS-0142 gracefully and note it was requested via Dex
>Put SRV-BACKUP-02 in maintenance mode for the next hour while we troubleshoot

Employee prompts

>Is my laptop online in NinjaOne? When did it last check in?
>Am I behind on updates?
>Something keeps alerting on my machine - what is it?

Policy actions

Every action Dex can take on NinjaOne is declared, scoped, and guardrailed. Admins control which apply, who approves them, and whether they're limited to self-service.

Action	What it does	Guardrails
`ninjaone_check_device_status`	Check device status, last contact, and inventory details	self-only
`ninjaone_check_patch_status`	Check OS-patch status and install history	self-only
`ninjaone_view_alerts`	View active monitoring alerts	self-only
`ninjaone_run_script`	Run an Automation Library script or built-in action on a device	approval
`ninjaone_reboot_device`	Reboot a device (graceful or forced)	approval
`ninjaone_set_maintenance`	Open a maintenance window on a device	approval

How to configure NinjaOne

Onboarding takes minutes. Dex validates your credentials before saving them.

Setup steps

1
In NinjaOne, go to Administration > Apps > API > Add and create an API Services (machine-to-machine) application.
2
Grant the app the scopes Dex needs: Monitoring (read), Management (device/org writes), and Control (remote actions).
3
Copy the Client ID and Client Secret, and note your instance region (US, EU, US2, CA, or OC).
4
In Dex, enable the NinjaOne integration and paste the instance URL, Client ID, and Client Secret.
5
Dex validates the credentials with a live call before saving. For MSPs, deploy as a global app and map each customer tenant to its NinjaOne Organization id.

Credentials required

instance_url: NinjaOne instance host for your region (e.g. app.ninjarmm.com, eu.ninjarmm.com)
client_id: OAuth2 client id of the API Services application
client_secret: OAuth2 client secret of the API Services application
organization_id: Optional NinjaOne Organization id - when set, every call is confined to that organization (per-customer MSP isolation)

Requirements

•A NinjaOne account with API access and an API Services (client-credentials) application
•Scopes granted to match what you enable: Monitoring for reads, Management for writes, Control for remote actions
•Script execution requires a user-context token in NinjaOne - a client-credentials connection can read, alert, reboot, and manage, but NinjaOne may refuse script runs without user context
•For MSPs, the integration deploys as a global app with per-tenant Organization scoping

Related integrations

See Dex run NinjaOne

Book a 30-minute walkthrough with our team and see how autonomous IT works in your environment — or get started for free.

Book a Demo Browse all integrations →