Schedule a Script

AUTOMATIONOPENFRAMESCRIPTSTUTORIAL

Phase 5 — Scripts & Automation · Step 4

Section

June 19, 2026

Published

Vladislav Marchenko

Vladislav Marchenko

Head Of Marketing

Schedule a Script

Phase 5 — Scripts & Automation · OpenFrame Onboarding

Some scripts shouldn't wait for you to remember them — nightly cleanups, weekly reports, a one-time run at 2 a.m. when nobody's working. The Scripts Schedules tab lets you set a script to run at a date and time, optionally on repeat, against the devices you choose.


Before you start

  • The script you want to schedule already exists in your Scripts List (build one first via Create Your First Script).
  • You know the devices (or device tags) it should hit.
  • You've decided the cadence — one-time, or every N days/weeks/months.

Create the schedule

Go to Scripts → Scripts Schedules → Add Schedule. You'll get the New Script Schedule form.

  1. Schedule Name — what this run is, e.g. Nightly Temp Cleanup.
  2. Select Date and Select time — when it first runs.
  3. Repeat Script Run — tick this to make it recurring. You then set an interval (a number) and a unit: Day, Week, or Month (e.g. every 1 Day). Leave it unticked for a one-time run.
  4. Supported PlatformWindows or MacOS, so the script targets the right machines.

Add the script(s)

Under Scheduled Scripts:

  • Select Script from the dropdown (it lists scripts matching your chosen platform).
  • Each script gets its own Timeout, and you can Add Script Argument / Add Environment Var for that script — same input rules as a manual run (match the field to what the script reads).
  • Click Add Script to chain more than one script into the same schedule.

Then click Save Schedule.


Assign the devices

Here's the part that's easy to miss: devices are assigned separately from the schedule itself. On the Scripts Schedules list, open the schedule's "…" menu and choose Edit Devices.

That opens the Schedule Devices picker — the same selector you've seen on monitoring policies:

  • Select Specific Devices — tick individual machines (this is the mode available today).
  • Select Devices by Criteria — auto-include current and future devices matching criteria. Marked COMING SOON.
  • Use Available Devices / Selected Devices tabs, Search, the Device Tags filter, or Add All Devices, then Save Devices.

The schedule's Devices count on the list reflects what you assigned.


Manage it later

On the Scripts Schedules list each row shows the Script, OS, Date & Time, Repeat (e.g. Daily / Once), and Devices count. The "…" menu gives you Edit Schedule (timing and scripts) and Edit Devices (targets); the arrow runs/opens it.


Quick checklist

  • Named the schedule and set Date + Time
  • Chose one-time vs Repeat (interval + Day/Week/Month)
  • Selected the platform and added the script(s) with any inputs
  • Saved the schedule, then used Edit Devices to assign targets
  • Confirmed the Devices count looks right on the schedules list

What's next

Scheduled runs report back just like manual ones — Script Results & Output Logs shows you how to read the output and debug a failure.


Based on OpenFrame v0.9.19. "Select Devices by Criteria" is a roadmap item — re-check the console before treating tag auto-targeting as available.

Vladislav Marchenko

Head Of Marketing

Hi all! My name is Vlad and I’ve been brought on to head the marketing team at Flamingo. Thankfully, this isn’t the first time I will be building a marketing department from scratch, so the experience should come in handy. Now it’s time to dive into the world of MSPs and find myself in this new world.

Related Content

Product Releases

Webinars

Case Studies

Blog Posts

Frequently Asked Questions

MSP AI Agents

Yes. In production MSP shops today, 10% to 25% of tickets close before a human opens them. Thread alone has processed 173 million tickets across 750-plus MSP partners at 96% triage accuracy, handing back 490,000-plus technician hours. Agents own the low-risk, high-volume work (password resets, MFA enrollment, known installs, onboarding and offboarding) and flag anything that touches production data or needs judgment for a human to take.
On a five-person desk, reported deployments show $78,000 to $130,000 in annual direct labor savings, roughly 30% fewer escalations, and 15% to 20% better SLA compliance. Broader MSP adoption data adds ticket handling time cut by 45% and five to 12 points of margin, all from reclaimed capacity rather than headcount cuts.
An AI agent for an MSP is software that reads a ticket, decides the action, performs it across your tools, and records the result without a technician driving each step. It differs from a chatbot or copilot by taking action, not just suggesting one.

AI MSP

MSPs use AI to triage and route tickets, cut alert noise, schedule patches, assist L1 security work, and draft client reports. Kaseya's 2025 benchmark found 30% already use it to eliminate tedious tasks, with ticket triage the most common starting point.
Start with a readiness assessment, not a tool purchase. Confirm your ticket history is clean and your RMM, PSA, and monitoring systems connect. Then pick one high-volume, low-risk workflow, usually ticket triage, and pilot it on internal tickets before any client sees it.
Automate high-volume, low-risk tasks first. Ticket triage and alert noise reduction top the list because they run constantly and a human still resolves the underlying issue. Save security approvals, billing changes, and client-facing actions for later, always with a human in the loop.

AI for MSPs

Set a baseline before rollout, then track tickets closed per technician, mean time to resolution, percentage of tickets resolved with no human touch, technician hours reclaimed, and cost per ticket. AI-driven automation commonly cuts operational cost per ticket by 25 to 40%.
No. AI automates routine tickets, patching, and monitoring, but trust, accountability, and complex business judgment still need people. The future of managed services moves technicians from closing tickets to advising clients, which makes the human role more valuable, not obsolete.

About OpenFrame

OpenFrame isn't built to plug into your stack. It replaces it. Instead of duct-taping a dozen tools together (RMM, MDM, SIEM, patching, remote access, each its own login and bill), we bundle it into one unified platform: RMM, MDM, monitoring, automation, remote access, patch management, security monitoring, and ticketing, plus built-in AI copilots. So "does it integrate with X?" usually means: you won't need X anymore.

AI Infrastructure

AI-powered infrastructure managed services apply machine learning to infrastructure telemetry so providers can predict failures, automatically remediate known issues, and forecast capacity needs. They replace static-threshold monitoring and manual firefighting with predictive, largely automated operations overseen by technicians.