Appearance
Automation for MSPs
MSP automation across RMM, PSA and billing.
PowerShell, Bash and Python at the endpoint. Ticket workflows in the PSA. Recurring billing actions. All on one job runner, all on one event bus, all in one platform. No Zapier subscription required.
Automation in most MSP stacks splits three ways. Scripts live in the RMM. Ticket rules live in the PSA. Billing automations live in a spreadsheet or worse. When something fires, it crosses tool boundaries, loses context, and ends up as a "did that actually run?" question on a Slack channel.
OpsMerge runs all three classes of automation on one job runner, against one shared data model. A patch failure on Tuesday raises a ticket on the same platform that bills the asset. A high-priority ticket fires a script on the right endpoint without an integration layer in the middle.
Read the deep dive on scripts · See ticket workflows · See patch automation
- Scripts at the endpoint
PowerShell on Windows, Bash on Linux, Python where installed. Stored, scheduled or event-triggered. RBAC on who can author and run. Per-organisation concurrency caps.
- Ticket workflows in the PSA
Automated assignment, SLA escalation, status transitions, internal-note triggers. Driven from the same event bus the RMM publishes telemetry on.
- Billing automations
Recurring contracts auto-count assets, auto-issue invoices, auto-push to QuickBooks Online. Voids unwind the chain in one action.
- No middleware to babysit
No Zapier between the RMM and the PSA. No Make scenario between the PSA and the accounting tool. One job runner, one set of logs, one place to look when something misfires.
Worked examples
Automations MSPs actually run
Onboarding
New endpoint check-in fires a PowerShell baseline script, raises an onboarding ticket, and flips the asset to billable on the next cycle.
Patch failure
Patch run exits non-zero. Telemetry event publishes. PSA raises a ticket against the asset with the failing KB ID attached. Technician picks up the trail.
SSL expiry
Domain monitoring catches a cert 14 days from expiry. Auto-raises a ticket with priority bumped per the impact-urgency matrix.
Offboarding
Agent uninstall flips the asset to archived. Recurring billing line skips it. Audit-trail row remains for next month's review.
VIP escalation
Ticket raised by a VIP contact pre-empts the queue and triggers an SLA rule with tighter response targets.
Quote acceptance
Client clicks accept. OpsMerge atomically writes the invoice and opens the implementation ticket. One transaction.
Automation questions
What MSP operators ask about scripts and triggers
What can OpsMerge automation actually do?
Three classes of automation, one runtime: scripts at the endpoint (PowerShell, Bash, Python), ticket workflows in the PSA (assignment, SLA escalation, status transitions), and recurring billing actions. All driven from the same event bus.Are scripts sandboxed?
No. Scripts run with agent privileges (SYSTEM on Windows, root on Linux). They are admin tools. RBAC controls who can author, edit and run, with per-organisation concurrency caps to prevent thundering-herd events.Can I trigger automations from ticket events?
Yes. Ticket workflows fire on the same event bus the RMM publishes telemetry on, so a ticket comment can fire a remediation script on the right endpoint without an integration layer in the middle.Do I need Zapier or Make to connect things up?
No. The internal flows — RMM telemetry to PSA tickets, PSA ticket actions to RMM scripts, recurring billing to invoices — run on the platform job runner. Zapier-style middlewares still work for external systems once the public API ships post-GA.Can I import scripts I already have?
Yes. Paste in, upload as a file, or pull from a Git URL (post-GA). PowerShell, Bash and Python all run unchanged.
See your workflows on one platform
Bring your existing PowerShell, Bash and Python. They paste in unchanged. We will help with ticket rule mapping during beta onboarding.