Overview

An automation is a small workflow: one trigger decides when it runs, and an ordered list of steps decides what happens. When it fires, RAD creates one run per targeted device and executes the steps in order for that device. Steps can pause the run - to wait out a delay or to wait for a person to approve - which makes automations ideal for staged rollouts and change control, not just instant fixes.

Where Remediation is a single condition → single action reflex, Automations give you a visual builder, multiple sequential steps, scheduling, on-demand runs, and a live per-device history.

Triggers

• Manual - you press Run and pick the devices. Great for one-off maintenance you want to watch.
• Alert - fires when an RMM alert arrives and all of your conditions match (alert title, type, category, severity, source, hostname, OS, customer). It targets the alerting device.
• Device enrolled - fires automatically the moment a new device is approved. Perfect for onboarding: install software, set a folder, create a "new device" ticket.
• Scheduled - runs on a recurring schedule (hour, minute, and optional days of week) against a scope you choose - all devices, one customer, or one folder.

Steps

• Run a script from your script library on the device.
• Reboot the device (schedules a restart in 60 seconds with a user notice).
• Show a message on screen to the logged-in user.
• Move device to a folder - handy for re-organizing during onboarding.
• Create a ticket under the device's customer (or a customer you pick).
• Send an email or send an SMS to notify your team or the customer.
• Resolve the triggering alert (for the Alert trigger).
• Call a webhook to notify an external system.
• Wait / delay - pause minutes, hours, or days, then resume automatically.
• Wait for approval - pause until a technician approves the run from its history.
• Run another automation - call a different automation on the same device. Protected against loops: if it would call back into an automation already running in the chain, the run fails with the loop shown.
• Trigger point (re-entry) - an alternate entry point (see below).

Text fields in tickets, emails, SMS, and webhooks support placeholders like {{hostname}}, {{alert_title}}, {{alert_message}}, and {{severity}}.

Branches (Paths)

Add a + Add Path node to branch. A branch holds ordered, named paths, each with its own match conditions and its own steps. When a run reaches the branch, it takes the first path whose conditions all match for that device; a path with no conditions is the default. Paths are resolved per device, so the same automation can do different things on a server vs. a laptop.

Trigger points (re-entry)

A trigger point is an alternate entry point placed among your steps. When a matching alert fires on a device, the automation starts running from that step downward - the steps above it are skipped for that run. During a normal top-to-bottom run the trigger point is simply passed through. Trigger points only act as entry points at the top level of the automation; one placed inside a branch path is ignored. This lets a single automation define an onboarding flow at the top and a separate "when disk fills up" flow lower down, without a second automation.

Building an automation

1. Open Automations in the sidebar and click + New Automation.
2. Give it a name, pick a trigger, and fill in the trigger's settings (conditions, schedule, or scope).
3. Click + Add step (or + Add Path to branch) and configure each step. Reorder by grabbing a step's handle and dragging it above or below another (or use the up/down arrows).
4. Optionally tick Continue even if this step fails on steps that shouldn't stop the run.
5. Save. Toggle it on or off any time from the list.

Running & watching

Manual and scheduled automations show a Run button - press it, choose devices (or accept the default scope), and the run starts. Click History on any automation to see every run with its status:

• Running - steps are executing.
• Waiting - paused on a delay or awaiting approval. Open the run to Approve & continue or Cancel.
• Completed / Failed / Cancelled - terminal states. Open a finished run to see the per-step timeline and outputs, or Re-run on this device.

The history and the run detail refresh live, so you can watch a staged rollout move device by device.

Example automations

• Device enrolled → move to "New Devices" folder → run the standard-apps install script → create an onboarding ticket.
• Scheduled nightly → run disk cleanup → wait 5 minutes → reboot.
• Alert: "Backup failed" → create a high-priority ticket → send the team an SMS.
• Manual "Patch & reboot servers" → run updates → wait for approval → reboot.