Security
Huntress integration
Use Huntress? Connect it to MSProspector to find upsell revenue in your clients. Built for MSPs who want more leads, marketing and sales.
Reads which Huntress agents have stopped checking in. View-only.
Setup steps are for connected customers — sign in to read them.
What we find in Huntress
Agents that have gone quiet (no survey check-in past 7 days) — an overlay on the RMM's fleet, not a second one. OS/hardware facts not yet wired: no confirmed field names beyond organization identity and survey timestamp.
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 Huntress connection does
Read — powers Client Upsell
Read your clients' stack
Who is actually protected: endpoints still onboarding, seats never deployed, sites with no filtering policy.
Permissions to prepare with your administrator
Required permissions and account access
- User API Credentials for a dedicated read-only user. The API Key and Secret inherit that user's permissions.
Which accounts and records: The user must see the intended organizations and agents. Keep the user active and supply both parts of the credential.
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 Huntress
You make a view-only key using our setup steps. Our connection has no code that can write to Huntress, and your key is encrypted and only used to read.
Huntress integration — common questions
- How does the Huntress integration help my MSP get more leads and sales?
- Client Upsell reads Huntress 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 Huntress integration read?
- Reads which Huntress agents have stopped checking in. View-only.
- What does MSProspector find in Huntress?
- Agents that have gone quiet (no survey check-in past 7 days) — an overlay on the RMM's fleet, not a second one. OS/hardware facts not yet wired: no confirmed field names beyond organization identity and survey timestamp.
- Is the Huntress connection read-only?
- Yes. We only ever read from Huntress — our Huntress 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.
