Skip to main content
When you connect your RMM with Neo, Neo gains visibility into all of your scripts and registered devices. Neo can then suggest relevant scripts to technicians working on tickets, or execute scripts directly against devices—monitoring jobs and taking automated actions based on the results. Neo also links each synced device to its PSA company so reports, automations, and agents know which customer it belongs to — see Device mapping for how that works and how to correct it. You can connect more than one RMM at the same time — for example your main RMM plus ScreenConnect, or two RMMs during a migration. Each connected RMM gets its own card on the Integrations page with independent credentials, sync, and last-sync status, and every synced device and script stays tied to the RMM it came from, so agents always act through the right platform.
Setting up your RMM with Neo is a simple process. You will need to generate API credentials for your RMM and then configure the integration in Neo.

​
Use Cases

Neo’s RMM integration enables two powerful categories of automation:

​
Issue Remediation — Zero Human Touch

Neo can automatically execute scripts to resolve common issues without technician intervention:
  • Software management — Installing, updating, or repairing applications
  • Device maintenance — Rebooting devices, clearing caches, removing temp files
  • Service management — Starting, stopping, or restarting services and processes
  • Any typical RMM task — If you have a script for it, Neo can run it
You control the level of automation. Neo can either execute scripts automatically or request approval from a technician before taking action.
After executing a script, Neo monitors the job and takes intelligent follow-up actions based on the result:
  • Success — Close the ticket and notify the end user
  • Failure — Escalate to a technician or try an alternative remediation
  • Partial success — Document findings and recommend next steps

​
Revenue & Opportunity Creation

Neo can identify upsell and service opportunities by combining RMM data with intelligent automation.
When a device triggers an alert for 95% disk usage:
  1. Neo receives the ticket and runs a cleanup script
  2. Neo waits for the result (disk usage drops to 90%)
  3. Neo checks the device age from your RMM
  4. If the device is over 5 years old, Neo automatically messages the customer:
“Your device is over 5 years old and running low on storage. Would you like a quote for an upgrade?”
This transforms a routine maintenance ticket into a potential hardware sale.
When Neo detects a pattern of repeated issues on a device:
  1. Neo resolves the immediate issue
  2. Neo analyzes ticket history for the device
  3. Neo identifies the recurring pattern
  4. Neo reaches out to the customer suggesting a proactive maintenance plan or device refresh
Configure Neo’s automation rules to match your business processes. You decide which actions Neo takes automatically and which require human approval.

​
Supported RMM Platforms

Select your RMM platform to view the complete setup guide:

ConnectWise Automate

Connect using API credentials with dedicated user class permissions.

ConnectWise Asio

Connect using API access credentials. Script suggestions and execution supported.

Datto RMM

Integrate using API key and secret with administrator security levels.

N-Able N-Sight

Connect using API key authentication with monitoring permissions.

N-Able N-Central

Integrate using role-based permissions and dedicated API user.

NinjaOne

Connect using secure OAuth authentication flow—no API keys required.

Kaseya VSA X

Connect using a Third-Party Token (Token ID + Token Secret) from your VSA X tenant.

Syncro RMM

Connects automatically with the Syncro PSA. Note Neo cannot run or report on scripts through Syncro’s API.

Addigy

Connect with one API key. Manages Apple devices only. Agents find and run Addigy scripts through the shared RMM script tools, and run ad-hoc commands through the RMM API tool.

​
Quick Setup Summary

​
When an agent reports the RMM is not fully configured

An agent that tries to read from your RMM may answer with a message like:
NinjaOne is connected for this client but not fully configured: its region is missing. Retrying will not help — every NinjaOne call fails the same way until an administrator reconnects NinjaOne on the Integrations page of the Neo dashboard.
This means the RMM card shows as connected, but Neo cannot build a single call to that platform. Either a credential it needs is not stored — the NinjaOne region, or an API URL, key, or secret for a credential-based RMM — or, for NinjaOne, the stored authorization has expired or been revoked. The message tells the agent to stop calling that RMM for the rest of the run, carry on with the checks it can still do, and record the ones it could not. To fix it, open the Integrations page, disconnect the RMM named in the message, and reconnect it — the connect flow writes the full credential set in one step. Scheduled agents pick the RMM up on their next run. Reconnecting does not replay a run that already finished, so for a ticket an agent handled without its RMM checks, open the agent in Executions and use Run now on that ticket (see Agents).
Neo names the platform and what is wrong with it in the message rather than reporting a server error, so the message can tell the agent to stop calling that RMM instead of retrying a call that cannot succeed.
All integrations can be configured from the Neo Agent Dashboard. Navigate to the RMM section and select your platform to begin.