Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt

Use this file to discover all available pages before exploring further.

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; 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
  • 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.

Safety

ControlBehavior
Technician-in-the-LoopRequire human approval before any script runs — strongly recommended until you trust the agent’s choices
Script library is yoursThe agent can only run scripts that already exist in your RMM — it can’t write new ones
Custom instructionsTell the agent which scripts to prefer, which to avoid, and when to escalate instead of running anything
Test modeWhen test mode is on, the agent picks the script and device but doesn’t run anything

How to Configure

1

Connect an RMM that supports script execution

2

Enable RMM script execution

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

Set approval requirements

Start with technician approval on. 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.