Skip to main content
Neo Agents read your RMM through a single API-backed tool — NinjaOne RMM API, Datto RMM API, N-Sight RMM API, N-Central RMM API, ConnectWise Automate API, ConnectWise Asio API, Kaseya VSA X API, ConnectWise ScreenConnect API, Syncro RMM API, or Addigy API, depending on which RMM you’ve connected. It gives the agent the device and monitoring context it needs to triage tickets, pick the right remediation, and spot upsell opportunities.
The RMM API tool appears in your agent automatically once you connect an RMM — there’s no separate toggle in the tool list. You control what it can do on the workflow’s Integrations tab. To run scripts on a device, see Execute RMM Script.
ConnectWise ScreenConnect is a remote-support tool rather than a full RMM, so its API is organized around sessions (the installed access agents). Its permission groups are Sessions (read device/session data; manage session metadata), Commands (run a command on an endpoint), and Toolbox & Messaging. Because a command runs with the agent’s privileges (SYSTEM on Windows, root elsewhere), keep Commands read-only — or turn on Require approval for it — unless you intend the agent to run commands autonomously.
Syncro RMM has a much smaller API than the other RMMs, so its tool has two permission groups rather than the usual six or seven:
  • Devices — managed devices, their installed applications, and Windows patch status. Write additionally allows creating an asset and updating one’s name, customer, serial, type and properties.
  • Alerts — read, mute, raise, and resolve RMM alerts. Resolving is behind its own Resolve toggle and always asks for technician approval, because it clears the alert off your technicians’ console and can’t be undone from Neo.
Syncro script execution is not available to agents. Syncro’s schedule endpoint reports no result — no run id, no output — so an agent could never tell you whether a script ran or what it did. Rather than offer that blind, Neo leaves it out: Execute RMM Script does nothing on Syncro, and scripts stay a technician action in the Syncro console.
Addigy manages Apple devices only (Macs, iPhones and iPads). Its tool has seven permission groups:
  • Devices & Facts: search devices by any device fact, and read installed apps, certificates, custom facts and child organizations. Write sets static field values on devices.
  • Alerts & Monitoring: read received alerts, monitoring items and system events. Write acknowledges, mutes and resolves alerts.
  • Scripts & Commands: read the script library and earlier command output. Write runs a command or script on named devices, as root on a Mac. The agent runs scripts from your Addigy library through Execute RMM Script and ad-hoc commands through this tool.
  • MDM Device Actions: restart, shut down or rename a device, unlock a user account, and turn lost mode off.
  • Policies: read policies, MDM profiles, declarations, compliance and benchmarks. Write moves devices between policies, deploys a profile and forces a declarative management sync.
  • System Updates: read installed and available OS updates. Write schedules an update install on named devices, which can restart them.
  • Users: read Addigy console users and end-user device assignments. Write assigns a device to an end user.
The agent calls only the Addigy endpoints Neo supports: the reads in these groups and the actions listed above. Neo refuses any other Addigy write before sending it. Some actions always ask for technician approval, whatever the group is set to: erasing, locking or removing a device, turning on lost mode, rotating the FileVault key or the managed admin password, and creating, changing or removing an Addigy console user. The agent never reads the managed admin password or other stored secrets, and it has no access to billing, impersonation or TempAdmin.

​
What It Does

  • Look up devices and their details — OS, last check-in, online status, owner, organization
  • Map a ticket’s configuration item to the right RMM device
  • Check installed software and software inventory
  • Read open alerts and monitoring conditions
  • Check patch and OS-update status
  • Read backup status (where the RMM exposes it)
  • Map RMM organizations to your PSA companies
  • Reach any endpoint your RMM’s API exposes, gated by the permission groups you enable

​
Permission Groups

Each RMM integration is split into permission groups — for example Devices, Organizations, Software, Alerts, Automation, Backup, and others (the exact set varies by RMM). Every group has an access level: Most RMM use cases only need Read Only — the agent reads device and monitoring state to make decisions, and acts through Execute RMM Script.

​
Safety Controls

​
How to Configure

1

Connect your RMM

Set up the integration for your RMM platform.
2

Choose permission group access levels

On the workflow’s Integrations tab, set each RMM permission group to Read Only or Read / Write.
3

Enable script execution if needed

Turn on the RMM scripting permission to let the agent find and run scripts — see Execute RMM Script.
Pair the RMM API with your PSA and documentation tools: the agent can read a disk-space alert, check the device age in the RMM, run a cleanup script, and — if the device is old — message the customer about a refresh. That’s a maintenance ticket turned into a hardware quote.