Skip to main content
This tool lets a Neo Agent find a relevant script in your RMM’s library, run it on the right device, wait for the job to finish, and act on the result — close the ticket on success, escalate or try an alternative on failure. It’s how Neo does zero-touch remediation.
Enabled automatically when you turn on RMM script execution on the workflow’s Integrations tab — there’s no separate toggle in the tool list. Requires a connected RMM that supports script execution (NinjaOne, Datto RMM, N-Sight, ConnectWise Automate, ConnectWise Asio; more in progress). For read-only device and monitoring data, see RMM API.

​
What It Does

  • Search your RMM’s script library by description and match it to the ticket’s issue
  • Resolve the ticket’s configuration item to the right RMM device
  • With several RMMs connected, run on the exact RMM the device belongs to — if a device ID matches devices in more than one RMM, the agent is shown the candidates and picks one explicitly instead of guessing
  • Run the script on that device
  • Wait for the job to complete and read its output
  • Verify the issue is resolved, then take follow-up action — close and notify, escalate, or try another fix
Finding scripts, executing them, waiting for results, and reading output are all part of this capability — you don’t enable them separately.

​
Burst Protection

RMM devices run one job at a time, and RMM platforms expire jobs that don’t start in time (Datto RMM: 60 minutes). When many jobs target the same device at once — end-of-month change requests, bulk maintenance — Neo holds the excess in a dispatch queue and releases each job as the device frees up, so every job runs inside its execution window instead of expiring in the device’s backlog. Queued jobs show as queued in Event History and dispatch automatically — no action needed. A job that can’t be dispatched within 8 hours (device offline or saturated) is marked failed with a clear reason.

​
Safety

When technician approval is enabled for this tool, the agent must obtain an actual approved Technician-in-the-Loop request before a script runs — it requests approval first, then executes once approved. Marking a script “pre-approved, no approval needed” in custom instructions does not waive this: custom instructions guide which scripts the agent prefers, but they can’t bypass the approval requirement. To let specific known-safe scripts run without a per-run approval, add them to the tool’s structured pre-approved scripts allowlist — matched exactly on the script and its parameters — rather than relying on a note. Everything not on the allowlist still requires approval, so you keep the guard where it matters while letting routine read-only diagnostics run immediately.
Where approval is set. Approval for script execution comes from Require Technician Approval on the permission group that grants scripting for your RMM — Datto RMM Jobs, NinjaOne / VSA X / CW Asio Automation, N-Sight Tasks, CW Automate Script Execution. Turning it on there gates script runs as well as that RMM’s API calls. If you connect several RMMs and any one of them has approval on, script execution asks for approval on all of them — the agent has a single approval setting covering every RMM.
Which devices the agent can target. A chat agent can run a script on any device in your synced RMM inventory — a technician naming a machine in chat is the instruction, and the ticket attached to the run is only used for logging. Ticket-triggered and scheduled agents are stricter: they can only act on devices belonging to the ticket’s company, so an automation can’t reach another customer’s machine.
ConnectWise Automate — script priority. Automate runs scheduled scripts by priority (1 lowest, 15 highest). Neo submits Automate scripts at 15 (highest) by default, so remediation runs right away instead of waiting behind lower-priority queued work. To make a specific script yield to your other Automate jobs instead, tell the agent in custom instructions to run it at a lower priority — for example, “run cleanup scripts at priority 5.” Other RMMs ignore this setting.
ConnectWise Asio. Neo runs Asio scripts by scheduling them on the endpoint. The agent reads each script’s parameters and fills them in — including the built-in “PowerShell script” template, whose body parameter takes an entire ad-hoc PowerShell payload (for example, download an installer and run a silent install). Grant the Automation permission group Read & Write to allow execution. Newly connected or changed scripts expose their parameters after the next RMM sync.

​
How to Configure

1

Connect an RMM that supports script execution

Set up NinjaOne, Datto RMM, or N-Sight.
2

Enable RMM script execution

On the workflow’s Integrations tab, turn on script execution for that RMM.
3

Set approval requirements

Start with Require Technician Approval on for that RMM’s script-execution permission group — the same toggle you used in the previous step. Add custom instructions about which scripts to prefer or avoid.
4

Watch the results

Review every run in Event History before widening automation.
Keep approval on while you build a track record. Once you’ve seen the agent reliably pick the right script for a class of tickets — password-reset agents, printer-spooler restarts, disk cleanups — you can turn approval off for just those.