RMM
SuperOps integration
Use SuperOps? Connect it to MSProspector to find upsell revenue in your clients. Built for MSPs who want more leads, marketing and sales.
Reads your clients, agreements, devices and tickets. View-only.
Setup steps are for connected customers — sign in to read them.
What we find in SuperOps
Clients, agreements, devices, tickets.
Every finding lands on your Client Upsell board as a named client with a number beside it — not a report you have to read.
What the SuperOps connection does
Read — powers Client Upsell
Read your clients' stack
Device posture: patch state, EDR, OS and hardware age, software EOL.
Permissions to prepare with your administrator
Required permissions and account access
- Dedicated technician role with view access to clients, contracts, assets and tickets only. The API token inherits that technician's role.
Which accounts and records: Use the correct subdomain and US/EU API region. The technician must be able to see all intended clients.
A green credential check proves access to the records tested. Confirm the expected data after the first pull; missing permissions or tenant consent must remain visible.
Read-only
We only ever read — we never change anything in SuperOps
You make a view-only key using our setup steps. Our connection has no code that can write to SuperOps, and your key is encrypted and only used to read.
SuperOps integration — common questions
- How does the SuperOps integration help my MSP get more leads and sales?
- Client Upsell reads SuperOps view-only and turns what it finds into upsell opportunities: each one a named client with a number beside it, ready for your account managers to sell.
- What does the SuperOps integration read?
- Reads your clients, agreements, devices and tickets. View-only.
- What does MSProspector find in SuperOps?
- Clients, agreements, devices, tickets.
- Is the SuperOps connection read-only?
- Yes. We only ever read from SuperOps — our SuperOps connection has no code that can change anything, and an automated check on every change to our code blocks any that could. Please create a view-only key using the setup steps, so the key itself can't make changes either.
