Managing IT environments through manual scripting has become increasingly inefficient for MSPs. Maintaining custom scripts, troubleshooting errors, and repeatedly running the same jobs consumes valuable technician time and introduces unnecessary risk. As environments grow more complex, relying on Script Jobs alone no longer scales.
That is why, over the coming weeks, Script Jobs will be phased out in favor of Automations. While Script Jobs served an important purpose, Automations remove key limitations and provide a faster, more flexible way to manage devices at scale. This shift also aligns with how modern MSPs approach automation, compliance, and patch management software as part of a broader RMM strategy.
To support this transition, a new resource library is available with ready to use automation templates and examples designed to simplify common workflows.
This shift reflects a broader move toward IT process automation, where repetitive operational tasks are standardized, scheduled, and executed automatically across large device fleets.
Why Automations Replace Script Jobs
Automations introduce capabilities that were difficult or impossible to achieve with Script Jobs alone.
Cross Platform Compatibility
Automations can run actions across multiple operating systems within a single workflow. This removes the need to maintain separate scripts for Windows, macOS, or Linux environments.
Offline Device Management
Tasks can now be queued for offline devices and executed automatically when they come back online. This ensures updates, fixes, and patch management software workflows do not fail silently.
Conditional Execution
Automations allow actions to run only when specific conditions are met. This reduces unnecessary executions and prevents misapplied changes.
Action Chaining
Multiple actions can be executed in sequence, creating structured workflows rather than isolated script runs.
Scheduling and Event Triggers
Automations can run on schedules or be triggered by events, supporting proactive maintenance and real time response.
Built In Retry Handling
Failed actions automatically retry, improving reliability without manual intervention.
Benefits of RMM Automation for MSPs
Automations represent a shift toward scalable, repeatable operations.
- No code workflows reduce reliance on custom scripting
- Greater flexibility through conditions and chained actions
- Set and forget execution with offline support and retries
- Improved scalability regardless of endpoint count
As MSPs manage larger fleets, automation becomes essential not just for efficiency but also for consistency. This is especially true when automation intersects with patch management software, where missed updates can create security and compliance risks.
How Level Is Making the Transition Easier
To minimize disruption, several changes are being rolled out gradually.
Script Library Migration
Scripts will move under Automations and will be executed only as part of an automation workflow. Scripts and Automations can now be grouped for better organization.
Jobs Section Update
The existing Jobs section will remain temporarily but will be phased out in a future update.
Run Script Action
Selecting “Run Script” will automatically create an Automation, queue devices, and replace the older Jobs based workflow.
Automation Improvements
Additional features are being added to ensure Automations match and exceed the functionality of Script Jobs. These include expanded output views, CSV export of results, and easier re runs for recent devices.
What’s Coming Next for Automations
Automation capabilities will continue to expand with features designed to reduce duplication and increase adaptability.
Variables Support
Variables allow dynamic data to be referenced inside scripts, actions, and triggers. Endpoint details such as hostname, IP addresses, and device metadata can be used to drive smarter workflows.
Custom Fields
Custom Fields enable storing client or device specific data directly within Automations. This makes it possible to reuse workflows across multiple clients without creating separate scripts.
Together, Variables and Custom Fields dramatically reduce script sprawl and support more advanced automation patterns. This level of flexibility is increasingly expected in platforms that also deliver modern patch management software functionality.
Automation and Patch Management
Automations play a critical role in how MSPs handle updates and remediation. Instead of relying on manual intervention, patching workflows can be automated, validated, and retried when needed.
If you’re already exploring patching solutions, our 5 RMM Patch Management Software (Free + Paid) guide shows how modern tools are evolving, and Level’s upcoming Automations are built with this same flexibility in mind.
Final Thoughts
Automations represent the next step in scalable device management. They eliminate the fragility of manual scripting and introduce reliability through structure, conditions, and retries.
As Script Jobs are phased out, Automations will become the foundation for everything from routine maintenance to advanced patch management software workflows. The goal is simple, help MSPs spend less time fixing scripts and more time delivering value.
We are excited for you to experience these changes and encourage you to explore the new Automation capabilities. As always, feedback is welcome, and the Level team is here to support you throughout the transition.
Stay tuned for more updates, and thank you for being a part of the Level community!