Skip to content

Write the fix once and let it run.

Scripts and automation is the scripting and remediation module in The One Stack, the platform MSPs run their whole business on. It keeps a script library, custom fields and automations that run on a schedule, a threshold or an event, for the technicians who manage client devices.

Scripts and automation is part of Endpoints, one of the six systems of The One Stack.

Illustration, sample data. A library script with its body, its risk level and the account it runs as.

What it does.

A script library

Keep PowerShell, Bash, Python and Batch scripts in one library. Built-in scripts copy into drafts you can edit.

Risk levels and run-as

Each script carries a risk level and runs as the user or as the system. A role sets the highest risk a person can run, and system-level runs are audited.

Custom fields

Define a field once, then set its value globally, per client or per device. The closest value wins, and scripts read it as a variable.

Automations with safeguards

An automation starts on a schedule, a threshold or an event, then runs a script, notifies someone, raises an alert or opens a ticket. A dry run, a device limit and optional approval keep a mistake small.

Runbooks

A runbook is a trigger and an ordered set of steps. Start from the built-in library or write your own.

Inside scripts and automation.

More of the product, screen by screen.

Run history

Each run of a script is kept as a job with its status, its exit result, its step results and its output. The job names who executed it, so a run by THEO reads the same as a run by a technician.

Illustration, sample data. Every script run is a job with its steps, its output and the name of who ran it.

How it connects.

Scripts and automation reads and writes the same record as the rest of the platform.

An alert triggers remediation

An alert from monitoring can start an automation on the device that raised it. Destructive actions wait for approval.

Monitoring and alerting

An automation opens a ticket

Opening a ticket is one of the actions an automation can take, so work that needs a person reaches the service desk.

Service desk

THEO runs the same scripts

When a runbook covers a fix, THEO dispatches the script through the same path your technicians use, with an audit trail.

Tier Zero

What THEO does here.

THEO runs a fix on its own when a runbook covers it, such as a full disk or a stuck print queue. Outside a runbook it asks or hands the work to a person.

THEO

Questions

Questions about scripts and automation

Which script languages does it run?

PowerShell, Bash, Python and Batch. Scripts run as the signed-in user or as the system.

Can any technician run a destructive script?

No. Each role has a ceiling on the risk level it can run, and destructive actions in an alert-triggered automation wait for approval.

How do I test an automation before it touches devices?

Run it as a dry run first. Then scope it to one client, group or device and set a device limit before you widen it.

Start

Run on One.

Start a trial and bring one client across, or book a walkthrough and follow a call down the line with us.