Automation scripts

Overview

Automation Scripts let technicians run scripts on devices on a schedule, in response to a threshold, or when a specific event happens — without any manual intervention. Use automations to handle routine tasks like disk cleanup, service restarts, or alert-triggered remediation automatically.

Creating an Automation

1. Go to Automation in the RMM navigation.
2. Click New Automation.
3. Give it a name that describes what it does.
4. Choose a trigger:
   • Schedule — runs at a fixed time, such as every day at 2 AM or every Monday at 6 PM.
   • Threshold — runs when a metric crosses a value, such as disk free falling below 10%.
   • Event — runs when something specific happens, such as a device going offline or a patch failing.
5. Select the target devices — a specific device, a device group, a client, or all devices.
6. Add an action: run a script, send a notification, create an alert, or open a PSA ticket.
7. Save.

Testing an Automation

Before enabling an automation, click Run Now to trigger it once immediately on the selected devices. Review the results to confirm the script behaves as expected.

Click Dry Run on threshold or event automations to see which devices would be targeted right now without actually executing anything. The dry-run output shows the evaluator's reasoning.

Enabling and Disabling

Automations are inactive by default until you toggle Enabled. You can disable a running automation at any time. Disabled automations do not fire until re-enabled.

Use Clone to copy an existing automation as a starting point for a new one.

Viewing Script Output from Automations

When an automation runs a script, each execution appears in the Script Runs history on the affected device and in the fleet-wide run history under Scripts > Run History. Click a run to see stdout, stderr, exit code, and duration.

Script Library

Scripts used in automations come from your organization's script library. To add a script:

1. Go to Scripts.
2. Click New Script and paste your PowerShell or Bash code.
3. Save it. It will appear as an option when building or editing automations.

You can also import from the Community Scripts library — scripts shared by other MSPs on the platform.

Frequently Asked Questions

My threshold automation is not firing even though the metric is over the limit.

Threshold automations evaluate every five minutes. Allow one full cycle after the condition is met. Open the automation and click Dry Run to see whether the evaluator picks up the current state.

Can I run an automation immediately on one device to test it?

Yes. Click Run Now from the automation detail. This fires it once immediately regardless of the trigger schedule.

Will an automation run on devices that are offline at the scheduled time?

For scheduled automations, the command is queued and delivered the next time the device heartbeats. The device will run it when it comes back online.

How do I prevent an automation from firing during a maintenance window?

Create a maintenance window and enable the "Pause automations" option. The automation will not fire for covered devices during the window.

Related

• Remote Commands
• Monitoring Alerts
• Maintenance Windows
• Device Groups