NinjaOne uses OAuth 2.0 for authentication, which provides a secure and simple setup process. No API keys to manage—just authenticate through the consent flow.
Prerequisites
Before starting the integration setup, ensure you have:- Admin Access: Administrator access to your NinjaOne instance
- OAuth Consent: Ability to approve third-party application access
- Region Information: Know which region your NinjaOne instance is hosted in
Setup Guide
1
Select your region
Navigate to the Neo Agent Dashboard and select NinjaOne from the RMM integrations.Select your NinjaOne region from the dropdown. This must match the region where your NinjaOne instance is hosted:
| Region | Description |
|---|---|
| US | United States data center |
| EU | European Union data center |
| OC | Oceania (Australia/New Zealand) data center |
2
Authenticate with NinjaOne
Click the Authenticate button to start the OAuth consent flow.A popup window will open directing you to NinjaOne’s authentication page:
- Log in with your NinjaOne administrator credentials
- Review the permissions Neo Agent is requesting
- Click Authorize or Allow to grant access
You must be an administrator of your NinjaOne instance to complete the consent flow. Standard users cannot authorize third-party integrations.
3
Complete the consent flow
Once you’ve authorized access, you’ll be redirected back to Neo Agent.
The integration status will update to show NinjaOne is connected. Neo Agent now has access to your devices and scripts.
OAuth Permissions
When authorizing Neo Agent, you’ll grant access to the following:| Permission | Purpose |
|---|---|
| Devices - Read | Access device information and inventory |
| Devices - Manage | Execute scripts and management tasks |
| Scripts - Read | Browse available automation scripts |
| Scripts - Execute | Run scripts on managed devices |
| Alerts - Read | Access monitoring alerts |
| Alerts - Manage | Clear and acknowledge alerts |
| Organizations - Read | Access client/organization information |
What Neo Can Do
With NinjaOne connected, Neo Agent can:Script Execution
Script Execution
- Browse your script library organized by categories
- Execute scripts on specific devices or device groups
- Monitor script job status in real-time
- Process script output for automated decision-making
Device Management
Device Management
- Search devices by name, serial number, or other attributes
- Access comprehensive device details and specifications
- View installed software and running processes
- Identify devices associated with end users or organizations
Monitoring and Alerts
Monitoring and Alerts
- Access active alerts and monitoring conditions
- Process alerts for automated remediation
- Clear alerts after successful resolution
- Correlate device status with ticket context
Organization Management
Organization Management
- Access organization/client information
- Map organizations to PSA companies
- Filter devices and scripts by organization
Managing the Integration
Refreshing Authorization
OAuth tokens automatically refresh, but if you encounter authentication issues:- Navigate to the NinjaOne integration in Neo Agent
- Click Reconnect or Re-authenticate
- Complete the OAuth flow again
Revoking Access
To disconnect Neo Agent from NinjaOne:- In Neo Agent: Navigate to integrations and click Disconnect for NinjaOne
- In NinjaOne: Go to Administration → Apps and revoke access for Neo Agent
Troubleshooting
OAuth Popup Blocked
OAuth Popup Blocked
- Check your browser’s popup blocker settings
- Allow popups from
dashboard.neoagent.io - Try using a different browser
Wrong Region Selected
Wrong Region Selected
- Disconnect the integration in Neo Agent
- Verify your region by checking your NinjaOne login URL
- Reconnect with the correct region selected
Consent Flow Fails
Consent Flow Fails
- Ensure you’re logged into NinjaOne as an administrator
- Check that third-party app access is not disabled in your NinjaOne settings
- Contact NinjaOne support if organization policies restrict OAuth apps
Devices Not Appearing
Devices Not Appearing
- Verify the OAuth authorization completed successfully
- Check that your NinjaOne user has access to the relevant organizations
- Ensure devices are active and checking into NinjaOne
