Integrations
AI for SuperOps
SuperOps puts your PSA and RMM on one platform. Connected to Control Center, tickets are triaged with each client’s business context, your standards are checked on every device each morning, and your team can ask about any client in Claude or ChatGPT.
Automations with SuperOps
Work that runs on its own, across your tools. A person approves the steps that matter.
Alerts become one ticket, with the fix attached
SuperOps alerts are grouped and duplicates dropped. One SuperOps ticket opens with the device, the user and the fix from IT Glue.
With IT Glue
Threats triaged before a tech looks
When Huntress flags a threat, a priority SuperOps ticket opens with who uses the device and what it can reach.
With Huntress
Isolation, approved from the ticket
A tech approves from the SuperOps ticket and Huntress isolates the device. Releasing it works the same way.
With Huntress
Known fixes run when a tech approves
For a repeat issue, the fix your team wrote in IT Glue runs through SuperOps, and the time lands on the SuperOps ticket.
With IT Glue
New hires set up from one request
A request in SuperOps creates the user in Microsoft 365 with the right groups and licenses, documents them in IT Glue and closes the ticket.
With Microsoft 365 and IT Glue
Offboarding that misses nothing
One SuperOps ticket blocks sign-in in Microsoft 365, removes licenses and closes with a record of every step.
With Microsoft 365
Failed backups handled overnight
When a Datto BCDR job fails, a SuperOps ticket opens with the error, the last good backup and the device’s health from SuperOps.
With Datto BCDR
Missed time entries caught daily
Tickets with work but no time in SuperOps are flagged to the tech each afternoon.
Every ticket triaged and routed
New SuperOps tickets are categorized, prioritized and routed, with the client’s business context attached.
Documentation that updates itself
Devices from SuperOps and users from Microsoft 365 sync into IT Glue every night, with changes flagged.
With IT Glue and Microsoft 365
Agreements and invoices reconciled
SuperOps agreements are checked against QuickBooks invoices every month, and anything unbilled is flagged.
With QuickBooks Online
New clients onboarded on rails
A new client in SuperOps gets a checklist that tracks SuperOps agents, Huntress coverage and Datto BCDR jobs until every device is done.
With Huntress and Datto BCDR
Full disks cleaned up before anyone calls
When SuperOps flags a disk filling up, the cleanup script your team approved runs. A SuperOps ticket opens only if that doesn’t fix it.
Failed patches retried, then explained
Devices that fail patching in SuperOps get another try in the next window. If one fails again, a SuperOps ticket opens with the error and the device’s history.
Software requests installed on approval
A software request in SuperOps installs through SuperOps once a tech approves it, and the ticket closes with what was installed.
New devices set up to your standard
When a new device checks in to SuperOps, your baseline scripts run and the device is documented in IT Glue.
With IT Glue
Password resets handled from the ticket
A reset request in SuperOps is done in Microsoft 365 once a tech approves it, and the ticket closes itself.
With Microsoft 365
Risky sign-ins investigated
A sign-in from an unusual country, or a burst of failed sign-ins in Microsoft 365, opens a SuperOps ticket with the user’s recent activity.
With Microsoft 365
MFA gaps turned into tickets
Users in Microsoft 365 without MFA open one SuperOps ticket per client, with the list attached.
With Microsoft 365
Failed restore tests caught early
When a Datto BCDR restore check fails, a SuperOps ticket opens before anyone needs that backup.
With Datto BCDR
QBR action items become tickets
Every action item agreed in a QBR becomes a SuperOps ticket or project, with an owner and a date.
Threats remediated on approval
A tech approves remediation from the SuperOps ticket, and Huntress cleans up the device.
With Huntress
Broken agents reinstalled
When an Huntress agent stops reporting, SuperOps reinstalls it with your script once a tech approves.
With Huntress
Standards checked in SuperOps
Checked every morning, for every client. Fewer tickets, better security, and every gap is a project you can sell.
Huntress on every device
Devices in SuperOps without a healthy Huntress agent become a ticket.
With Huntress
Patches inside your window
Every device in SuperOps, against the patch window you set.
Supported operating systems only
Devices in SuperOps on Windows or macOS versions past end of support.
Every server backed up
Servers in SuperOps with no Datto BCDR backup, or none that finished in the last 24 hours.
With Datto BCDR
Every client on a current agreement
Clients in SuperOps with an expired or missing agreement.
No stale devices or accounts
Devices in SuperOps that haven’t checked in for 30 days, and Microsoft 365 accounts unused for 90.
With Microsoft 365
Only approved software
Software in SuperOps’s inventory, checked against each client’s approved list.
No unapproved remote access tools
Remote access software in SuperOps’s inventory that isn’t on your approved list, at every client.
Every device has an owner
Devices in SuperOps that aren’t matched to a person in Microsoft 365.
With Microsoft 365
Every device documented
Devices in SuperOps that are missing from IT Glue.
With IT Glue
Leavers fully removed
Accounts in Microsoft 365 still enabled for people offboarded through SuperOps.
With Microsoft 365
Tickets closed properly
SuperOps tickets closed without notes or time, by tech. For you, not the client.
Reports from SuperOps
Numbers from your tools, in the client’s language. Build a report from any data you connect.
The whole QBR, drafted
SuperOps, SuperOps, Huntress and Datto BCDR in one QBR, written in the client’s business terms for your vCIO to approve.
With Huntress and Datto BCDR
Service desk, in business terms
Ticket volume, response times and repeat issues from SuperOps, explained by what they cost the client.
Patch compliance
From SuperOps, per device and per site.
Your margin on every client
Hours in SuperOps against revenue in QuickBooks. For you, not the client.
With QuickBooks Online
Devices by age and operating system
From SuperOps, per client and per site, with the devices due for replacement.
Software inventory
From SuperOps, with unapproved software called out.
Alerts and what they cost
Alert volume from SuperOps per client, with the SuperOps time spent on them. For you, not the client.
Response and resolution against your SLA
From SuperOps, per client and per priority.
Where the tickets come from
Tickets from SuperOps by person and by issue, so you fix the cause, not the symptom.
What AI did this month
Every AI service’s runs, hours returned and value, ready for the client’s QBR.
Standards scorecard
Every standard you check, passed or failed at each client, with each gap priced as a SuperOps project.
A one-page monthly summary
Tickets, devices, security and AI work from SuperOps and SuperOps, on one page for the client’s owner.
Any report you can describe
Describe it in a sentence. Control Center builds it from SuperOps and your other connected tools, then sends it on a schedule.
Ask about SuperOps in Claude or ChatGPT
Questions your team asks in Claude or ChatGPT, answered from every tool and client. Any answer can become a report or an automation.
“Which devices at Northbridge don’t have Huntress?”
Answered from SuperOps and Huntress.
“What did we do for Meridian this month?”
Answered from SuperOps and SuperOps.
“Which clients have more licenses than we bill for?”
Answered from Microsoft 365 and SuperOps.
“Why does Harbor’s file server keep alerting?”
Answered from SuperOps alerts and SuperOps history.
“What changed at Northbridge this week?”
Answered from SuperOps, SuperOps and Huntress.
“Turn that into an automation.”
Any answer can become a workflow, and a person approves it before it runs.
“Which servers at Northwind are low on disk space?”
Answered from SuperOps.
“Which patches failed at Meridian last night?”
Answered from SuperOps.
“Which computers still have the old VPN client?”
Answered from SuperOps’s software inventory.
“Which devices haven’t checked in this week?”
Answered from SuperOps.
“Has this happened at Harbor before? What fixed it?”
Answered from SuperOps ticket history and IT Glue.
“What can Sam at Northwind access, and which laptop is theirs?”
Answered from Microsoft 365 and SuperOps.
“What’s left on Meridian’s onboarding?”
Answered from SuperOps and IT Glue.
“What work did we do this month that we didn’t bill?”
Answered from SuperOps time entries and agreements.
“Which clients made us the least per hour this quarter?”
Answered from SuperOps and QuickBooks.
“Whose agreement renews next quarter, and what should we add to it?”
Answered from SuperOps agreements and each client’s AI roadmap.
“Draft Northbridge’s QBR.”
Built from SuperOps, SuperOps and every other connected tool, for your vCIO to edit.
“Clean up the disk on Harbor’s file server.”
Drafted as a SuperOps script that a tech approves before it runs.
Billing with SuperOps
Get paid for the AI work, through the tools you bill with.
AI services on the SuperOps agreement
Every AI service you sell is added to the client’s agreement and billed each month, at your margin.
Licenses matched to what you bill
Microsoft 365 licenses at every client against the SuperOps agreement, with missed billing flagged.
With Microsoft 365
Every AI run metered
Usage per client and per workflow, behind every line you bill.
What Control Center reads from SuperOps
Tickets, agreements, billing, time entries, devices, alerts, patching, scripts and software inventory.
Control Center connects to SuperOps through its public API. You add it once, then choose which clients it covers and which API operations it can use. The key goes in Control Center’s vault, never in a chat.
What you need: An API token from your SuperOps profile settings, plus your SuperOps subdomain.
The examples on this page use a stack MSPs often run with SuperOps: IT Glue, Huntress, Microsoft 365, Datto BCDR and QuickBooks Online. Build your AI plan to see them with your own tools.
Connection details and what you need from SuperOpsSee this example plan in the builder
Questions about SuperOps and Control Center
Does Control Center work with SuperOps?
Yes. Control Center connects to SuperOps through its public API and uses tickets, agreements, billing, time entries, devices, alerts, patching, scripts and software inventory. You add it once, then choose which clients it covers.
What can an MSP automate with SuperOps and AI?
With Control Center, 23 automations, including: alerts become one ticket, with the fix attached; threats triaged before a tech looks; isolation, approved from the ticket; known fixes run when a tech approves; new hires set up from one request; offboarding that misses nothing. A person approves the steps that matter.
Can I use SuperOps with Claude or ChatGPT?
Yes, through Control Center MCP. Your team connects Claude or ChatGPT once and can ask about SuperOps at every client, with the same roles and client scopes as their login. For example: “Which devices at Northbridge don’t have Huntress?”
What does it cost?
$1,750 a month for the Control Center platform plus $75 a month per billable workflow, with the first 90 days at no cost.