Overview

The Scripts section in the IT Automation module on the Unified Dashboard allows IT administrators to manage and maintain a library of script automations. These automations can be seamlessly accessed and executed directly through the bot.

Scripts are supported on both Windows and macOS devices. The operating system you select while creating a script determines the script language, the execution options available, how the script is run on the device, and which devices you can test it on — so pick it carefully. Once saved, the operating system cannot be changed for that script.

New script addition

Here's how IT admins can add a new script using the dashboard:

1. Click the "Add script" button in the top-right corner of the dashboard.

   

2. Enter basic details such as the script name, version, description, and operating system. You can also add tags to categorize the scripts.

   

3. Now add script details by either selecting from popular options available on the platform or by entering your own script information.

   

   To add a script from scratch, please provide the following details:

• Script type (Windows only): Choose whether the script is a Batch or a PowerShell script. Batch is the default. This field is not shown for macOS, where scripts are always shell (bash) scripts.
• Mode: Indicate the script type—whether it should proceed silently or require user interaction.
• Account type: Specify the privilege level the script should run with. The options are labelled per operating system:
  • Windows — System or User
  • macOS — Root or Local
  On macOS, when Mode is set to Interactive, the Account type field is hidden and the script always runs as Root.
• Script: Provide the script for automation or generate it using AI.

4. Finally, test your script by choosing a test device from the list mapped to the bot. The device list only shows devices matching the operating system selected in step 2. If testing succeeds, publish the script for end users. If testing fails, update the script details or select a different test device to try again.

   

📘

A script can only be published after a successful test execution, and only if the script content still matches what was tested. If you edit the content after a successful test, run the test again before publishing.

Windows configuration

Script type

Because PowerShell runs non-interactively, any host prompt in the script (for example, Read-Host) will fail immediately rather than hang invisibly. Ask for input using variables instead — see Variables in scripts.

Existing Windows scripts created before the Script type option was introduced are treated as Batch.

Mode and account type

Use System + Silent for unattended maintenance and inventory scripts. Use User only when the script must touch the employee's own profile, environment variables, or user-level registry hive.

macOS configuration

Script language

macOS scripts are always bash. The content is saved as a shell script and executed with /bin/bash. There is no Script type selector.

Mode and account type

🚧

Interactive macOS scripts rely on an active GUI session. For fleet-wide maintenance on machines that may be locked, asleep at the login window, or unattended, use Root + Silent.

Generate with AI

Turn on the Generate with AI toggle to describe what you need in plain language instead of writing the script yourself.

• Enter a prompt (minimum 5 characters) describing the task, then click Generate script.
• Generation is operating-system aware. On Windows, the output targets CMD or PowerShell depending on the Script type you selected. On macOS, the output is bash — multi-line scripts are supported.
• Mode and Account type must be set before generating, as they influence the command that is produced.
• The generated script appears in the editor and remains fully editable. Use Clear prompt to start over.
• If the prompt is unclear or asks for something unsupported, the platform returns a message instead of a script — refine the prompt and try again.

Variables in scripts

Scripts support placeholders written as {{variable}}. These are resolved just before the script is dispatched to the device:

• {USERNAME} — automatically replaced with the operating system username of the employee mapped to the target device. Preserve this exact spelling and casing; do not rename it.
• Custom variables — any other {{placeholder}} you add is detected automatically. When the script is triggered, the dashboard prompts for a value for each one.

If a placeholder cannot be resolved, the execution is rejected before anything runs on the device, so a malformed command is never dispatched.

Examples

:: Windows (Batch)
for /d %%D in ("C:\Users\{USERNAME}\*") do @echo %%D

# Windows (PowerShell)
Get-ChildItem -Path "C:\Users\{USERNAME}" -Directory | ForEach-Object { $_.FullName }

# macOS (bash)
ls -la "/Users/{USERNAME}/Documents"

Script details

The module's landing page displays a list of scripts with key details at a glance, including version, operating system, current status, addition method, tags, and who last updated them. It also offers filter and search options for quick discovery — including a filter by operating system. Clicking on any script item opens a detailed view with all configured information.

In the detailed view, the fields shown adapt to the script's operating system:

• Script type is displayed only for Windows scripts.
• Account type is shown as System/User for Windows and Root/Local for macOS, and is hidden altogether for macOS scripts in Interactive mode.
• The script body is syntax-highlighted as PowerShell, Batch, or shell depending on the operating system and script type.

Versioning

Once a script is published, its content becomes immutable to protect automations already in use. Editing the content of a published script creates a new version instead of overwriting the existing one, and you will be asked for a new version number. All versions stay linked to the same script, so past executions can always be traced back to the exact content that ran on the device.

Disabling a script

Published script can be disabled by selecting the "Disable" option from the three-dot menu on either the script row on the landing page or the details page. Once disabled, the script will no longer be available to employees on the bot, and any executions still pending for it are failed. Likewise, disabled script can be re-enabled in the same way.

Drafts

A script remains in draft state until it's published. During this time, details can be edited, or the script can be deleted from the three-dot menu on either the script row on the landing page or the details page.

Edit basic details

Basic details of published script can be edited by selecting the "Edit details" option from the three-dot menu, accessible on the script row on the landing page or the details page. The operating system cannot be changed once the script has been created.

Troubleshooting

Execution failures that relate to the operating system configuration usually map to one of the following:

Full logs, exit codes, and the exact content that was dispatched are available for every execution under Reports → Scripts.