Real Automations from Real MSPs
These automations run thousands of times per week across our users. Copy them, customize them, or use them as inspiration for your own.
67%
Avg Ticket Automation
18 hrs
Saved per Tech/Week
60 sec
To Create Automation
90+
Integrations
Ticket Automation
Reduce manual ticket handling by 67%
Slow Computer Diagnostic
Trigger: New ticket contains "slow" or "running slow"
Runs ~50/week for typical MSP
Automation Steps:
- 1.Run remote diagnostic script via RMM
- 2.Check disk space, memory, and CPU usage
- 3.Clear temp files if disk > 85% full
- 4.Update ticket with diagnostic results
- 5.Auto-resolve if issue fixed, else escalate
Password Reset Handler
Trigger: Ticket subject mentions "password reset"
Runs ~100/week for typical MSP
Automation Steps:
- 1.Verify user identity via security questions
- 2.Generate secure temporary password
- 3.Send reset link to verified email
- 4.Update ticket with actions taken
- 5.Close ticket automatically
New Employee Onboarding
Trigger: Ticket type = "New Employee Setup"
Runs ~10/week for typical MSP
Automation Steps:
- 1.Create AD account with department template
- 2.Provision Microsoft 365 license
- 3.Set up email with standard signature
- 4.Add to appropriate security groups
- 5.Send welcome email with login instructions
- 6.Create documentation in IT Glue
Printer Issue Triage
Trigger: Ticket contains "printer" or "printing"
Runs ~30/week for typical MSP
Automation Steps:
- 1.Check printer status via SNMP
- 2.Restart print spooler remotely
- 3.Clear print queue if stuck
- 4.Update drivers if outdated
- 5.Update ticket with resolution or escalate
Security Automation
Respond to threats in seconds, not hours
Failed Login Response
Trigger: 5+ failed logins detected for same user
Runs ~20/week for typical MSP
Automation Steps:
- 1.Temporarily lock account (15 min)
- 2.Send alert to user and IT
- 3.Log IP address and location
- 4.Create high-priority security ticket
- 5.If from new location, require MFA re-enrollment
Phishing Email Handler
Trigger: User reports email as phishing
Runs ~15/week for typical MSP
Automation Steps:
- 1.Quarantine email for all recipients
- 2.Block sender domain in spam filter
- 3.Check if any user clicked links
- 4.Reset passwords for affected users
- 5.Send company-wide phishing alert
- 6.Update threat intelligence
Endpoint Protection Alert
Trigger: Antivirus detects malware
Runs ~5/week for typical MSP
Automation Steps:
- 1.Isolate endpoint from network
- 2.Run full system scan
- 3.Collect forensic data
- 4.Create incident ticket with timeline
- 5.Notify security team via Slack/Teams
- 6.Reconnect after clean scan
Monitoring & Alerts
Proactive issue detection and resolution
Disk Space Warning
Trigger: Server disk space > 85%
Runs ~25/week for typical MSP
Automation Steps:
- 1.Analyze disk usage patterns
- 2.Clear Windows temp files
- 3.Empty recycle bins
- 4.Archive old log files
- 5.Alert if still > 80% after cleanup
- 6.Create capacity planning ticket
Service Restart Handler
Trigger: Critical service stops unexpectedly
Runs ~40/week for typical MSP
Automation Steps:
- 1.Attempt automatic restart
- 2.Check dependencies
- 3.Analyze event logs for root cause
- 4.Create incident ticket if restart fails
- 5.Notify on-call technician
- 6.Document in knowledge base
Backup Verification
Trigger: Daily at 6 AM
Runs Daily for typical MSP
Automation Steps:
- 1.Check backup job status across all clients
- 2.Verify backup file integrity
- 3.Test restore on sample files
- 4.Create tickets for failed backups
- 5.Generate weekly backup report
- 6.Alert if any client missed 2+ backups
Communication & Updates
Keep clients informed automatically
Ticket Status Updates
Trigger: Ticket status changes
Runs ~200/week for typical MSP
Automation Steps:
- 1.Send personalized email to client
- 2.Include summary of work done
- 3.Set expectations for next steps
- 4.Update client portal
- 5.Log communication in PSA
Maintenance Window Alerts
Trigger: 24 hours before scheduled maintenance
Runs ~10/week for typical MSP
Automation Steps:
- 1.Send reminder to affected clients
- 2.Post to client status page
- 3.Send internal reminder to team
- 4.Prepare rollback procedures
- 5.Send completion notification after
Monthly Report Generator
Trigger: First of each month
Runs Monthly for typical MSP
Automation Steps:
- 1.Gather metrics from all tools
- 2.Generate client-specific report
- 3.Include ticket stats, uptime, projects
- 4.Add AI-generated executive summary
- 5.Email to client stakeholders
- 6.Schedule QBR if metrics warrant
User Management
Streamline identity and access management
Employee Offboarding
Trigger: Ticket type = "Employee Termination"
Runs ~8/week for typical MSP
Automation Steps:
- 1.Disable AD account immediately
- 2.Revoke Microsoft 365 license
- 3.Remove from all security groups
- 4.Forward email to manager (30 days)
- 5.Backup user data to archive
- 6.Update documentation
- 7.Generate compliance report
License Optimization
Trigger: Weekly on Sunday
Runs Weekly for typical MSP
Automation Steps:
- 1.Audit M365 license usage
- 2.Identify inactive users (90+ days)
- 3.Flag unused premium licenses
- 4.Generate savings report
- 5.Create tickets for license review
Documentation
Keep your knowledge base current
Auto-Document Resolutions
Trigger: Ticket closed with resolution notes
Runs ~50/week for typical MSP
Automation Steps:
- 1.Extract key steps from resolution
- 2.Check if similar article exists
- 3.Create or update KB article
- 4.Tag with relevant categories
- 5.Link to related articles
- 6.Notify team of new documentation
Asset Discovery Sync
Trigger: New device detected in RMM
Runs ~30/week for typical MSP
Automation Steps:
- 1.Create asset record in documentation
- 2.Populate specs from RMM data
- 3.Assign to correct client/site
- 4.Link to warranty information
- 5.Add to network diagram
- 6.Create lifecycle tracking
AI Remote Control
Your AI sees, types, and fixes endpoints directly
Interactive App Troubleshooting
Trigger: Ticket mentions app-specific error message
Runs ~15/week for typical MSP
Automation Steps:
- 1.Take screenshot of current screen via XTS agent
- 2.AI analyzes visual layout to understand state
- 3.Navigate to app settings using keyboard/mouse
- 4.Modify configuration based on error pattern
- 5.Take verification screenshot showing resolution
- 6.Update ticket with before/after screenshots
Remote Registry Fix
Trigger: Ticket type = "Application Error"
Runs ~20/week for typical MSP
Automation Steps:
- 1.Connect to endpoint via XTS agent terminal
- 2.Run diagnostic commands to identify issue
- 3.Modify registry keys if needed
- 4.Restart affected services
- 5.Run validation script
- 6.Log all changes with before/after values
UI-Based Software Configuration
Trigger: New software deployment ticket
Runs ~25/week for typical MSP
Automation Steps:
- 1.Connect to machine, take initial screenshot
- 2.AI navigates setup wizard visually
- 3.Enter license key from secrets manager
- 4.Configure settings per company standards
- 5.Screenshot final configuration
- 6.Document settings in asset record
Visual Performance Diagnostics
Trigger: "Computer freezing" or "random crashes"
Runs ~30/week for typical MSP
Automation Steps:
- 1.Screenshot task manager and resource usage
- 2.AI analyzes visual data for anomalies
- 3.Run terminal commands for deep diagnostics
- 4.Kill problematic processes if needed
- 5.Monitor for 5 minutes, take status screenshots
- 6.Generate visual report for ticket
Ready to Automate Your MSP?
Create your first automation in under 60 seconds. Just describe what you want in plain English.
$5 per 1M tokens • Subscribe to our newsletter for $20 free credit