RMM
ConnectWise RMM (Platform) integration
Reads device posture (EDR, OS, hardware, disk, software). Read-only — the Current API only; this connector never speaks the deprecated Legacy Open API.
Setup steps are for connected customers — sign in to read them.
What we find in ConnectWise RMM (Platform)
Device posture — EDR, OS lifecycle, hardware age, disk headroom, software inventory. Distinct from ConnectWise Automate. Patch compliance not yet wired (separate endpoint, unconfirmed response schema).
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 ConnectWise RMM (Platform) connection does
Read — powers Client Upsell
Read your clients' stack
Device posture: patch state, EDR, OS and hardware age, software EOL.
Read-only, and checked
A write-capable credential is refused, not warned about
We test the key you give us the moment you submit it. If it can write to ConnectWise RMM (Platform), we reject it and tell you which step to change — there is no override. It is encrypted at rest, held in one vault in one application, and nothing is ever written back to ConnectWise RMM (Platform).
ConnectWise RMM (Platform) integration — common questions
- What does the ConnectWise RMM (Platform) integration read?
- Reads device posture (EDR, OS, hardware, disk, software). Read-only — the Current API only; this connector never speaks the deprecated Legacy Open API.
- What does MSProspector find in ConnectWise RMM (Platform)?
- Device posture — EDR, OS lifecycle, hardware age, disk headroom, software inventory. Distinct from ConnectWise Automate. Patch compliance not yet wired (separate endpoint, unconfirmed response schema).
- Is the ConnectWise RMM (Platform) connection read-only?
- Yes. The credential is checked live when you submit it and a write-capable one is refused, with no override — and every connector we ship is checked, at every commit, by an automated build rule that fails if it contains anything other than a GET call. The credential itself is wrapped by a key that lives in Azure Key Vault's hardware security module and never leaves it — our application can ask the vault to wrap or unwrap it, but cannot read the wrapping key. See our security page for the full picture.
