Integrations
Connect what you already run. Nothing new to deploy.
Integrations do three jobs here: they read your clients' stack so Client Upsell can find the revenue hiding in it, they deliver new signals into the CRM your team lives in, and they sync your PSA and your marketing system both ways. No agent to install, and nothing that can write to a client system without you mapping it first.
Deliver — powers Lead Signals
New signals land where your team already works
A signal nobody sees is worth nothing. These push it into the system your reps have open anyway, the morning it arrives — a CRM if you run one, and your PSA if the PSA is your pipeline, which for plenty of MSPs it is.
Live today
The Growth Machine (GoHighLevel)
When a new signal arrives, MSProspector automatically creates an opportunity, task, and notes in your Growth Machine account — so your team never manually enters a lead. Works with any GoHighLevel-based CRM in the MSP community.
Used by MSPs in these communities
- →Paul Green — MSP Marketing Edge
- →Nigel Moore — Tech Tribe / Growably
- →Chris Wiser — 7 Figure MSP / WiseTrack CRM
- →Nate Freedman — Tech Pro Marketing / MSPsites.com
- →Jumpfactor — Nexus CRM
Live today
Outbound Webhooks
Register any HTTPS endpoint and MSProspector will POST signal data as it arrives — or send a once-a-day batch. Wire into Slack, HubSpot (via Zapier or Make), or any custom platform without waiting for a native integration.
Hot alerts
Score ≥ 85 — fires within 2 min
Every new signal
Fires as signals route throughout the day
Daily digest
One batch per day with all new signals
Permissions and access requirements for every system
Open your system before asking its administrator for a key. Connect the systems your service uses; an optional tool you do not use does not need to be connected.
- Have the client's system administrator set the role and customer/site/tenant scope. Enter secrets only in the integration form, never in an email or ticket.
- Use Check and save, then inspect the first read/sync results. A successful authentication or company-list read does not prove agreements, tickets, device posture or all tenant consents are accessible.
- A 401 usually needs a current credential. A 403 names a permission or account-scope gap: fix that role/consent first. Never turn a write permission on just to repair a read.
- For Client Upsell, confirm the expected clients and agreements/contracts, plus the connected tool's data families. Unknown/unreadable is not zero coverage. For writes, review the preview with the client and obtain the required approval before enabling live writes.
WordPress website
Required permissions and account access
- For an Application Password, use a dedicated WordPress Editor or Administrator able to publish posts and upload media. Create the password under Users → Profile → Application Passwords.
- For the Marketopia plugin, the site's administrator installs/activates it and approves the site connection. Keep the plugin active and use the key for that site only.
Which accounts and records: Use the correct HTTPS site and an accessible WordPress REST API. A site ID or website URL alone does not authorize publishing. Save the Application Password or plugin key in the website form, never in a ticket. Publishing remains subject to the client's approval settings.
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.
Google Ads, Meta Ads, Microsoft Ads and LinkedIn Ads
Required permissions and account access
- The ad-account fields on My Connections save account/campaign identifiers; they do not grant provider access or establish that reporting works.
- The client's account administrator must separately grant access for the purchased reporting or campaign service through the provider's approved connection flow. Review the permissions shown there; reporting access does not require permission to launch or spend.
Which accounts and records: Record the client's own Google customer ID, Meta ad-account ID, Microsoft/Bing customer ID and LinkedIn campaign ID only for services they use. Confirm a report returns the intended account. A blank optional identifier is not an integration outage.
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.
LinkedIn, Facebook, Instagram and X social profiles
Required permissions and account access
- Profile URLs on My Connections identify pages; they do not authorize posting.
- For social publishing, the client administrator must connect the intended company pages/accounts in the Growth Machine Social Planner and approve the provider's displayed posting permissions. A personal profile URL is not a company-page grant.
Which accounts and records: Use the client's own pages and verify they appear in the publishing account. Optional profiles that the client does not use do not need to be connected. Posts remain subject to the client's approval settings.
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.
Webhooks / Zapier / Make
Required permissions and account access
- Use a receiver URL controlled by the client or their approved automation service. No PSA, RMM or mailbox administrator scope is granted by adding a webhook.
- Keep the webhook signing secret private and configure the receiver to verify signed events. The receiver must accept the events the client enables.
Which accounts and records: Select the intended receiver and event types for this client. Confirm the delivery log shows a successful receiver response after an authorized event; a disabled webhook is a choice, not a broken connection.
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.
The Growth Machine / HighLevel
Required permissions and account access
- View Contacts (contacts.readonly) — finding existing contacts, MQL and QBR counts, list health and data scans.
- Edit Contacts (contacts.write) — creating leads, notes, tags, tasks and workflow enrollment.
- View Opportunities (opportunities.readonly) — Load pipelines, deal sync and duplicate-deal checks.
- Edit Opportunities (opportunities.write) — creating deals from deal registrations, approved appointments, Lead Signals and AIDO replies.
- View Locations (locations.readonly) — confirming the token belongs to this client's sub-account.
- View Custom Fields (locations/customFields.readonly) — filling phone, title, industry and size fields on pushed leads.
- Edit Custom Fields (locations/customFields.write) — creating the fields PSA Sync and data buys write into.
- View Custom Values (locations/customValues.readonly) — reading the client's merge values for Campaign Studio.
- Edit Custom Values (locations/customValues.write) — saving landing-page links for Campaign Studio.
- View Tags (locations/tags.readonly) — choosing Campaign Studio audiences by tag, and QBR tag counts.
- View Users (users.readonly) — assigning each new deal to a team member, and picking who emails and posts are sent as.
- View Conversations (conversations.readonly) — call counts and talk minutes (dials).
- View Conversation Messages (conversations/message.readonly) — call recordings for call reviews.
- View Forms (forms.readonly) — form fills in the MQL count.
- View Calendars (calendars.readonly) — appointment requests in the MQL count.
- View Calendar Events (calendars/events.readonly) — appointment requests in the MQL count.
- View Email Campaigns (emails/campaigns.readonly) — Campaign Studio email sends (Emails section).
- Edit Email Campaigns (emails/campaigns.write) — Campaign Studio email sends (Emails section).
- View Email Schedule (emails/schedule.readonly) — email results on reports and launch checks (Emails section).
- Edit Email Schedule (emails/schedule.write) — scheduling Campaign Studio emails (Emails section).
- View Social Planner Accounts (socialplanner/account.readonly) — finding the client's social accounts to post to (Social Planner section).
- View Social Planner Posts (socialplanner/post.readonly) — post counts and checking Campaign Studio posts landed (Social Planner section).
- Edit Social Planner Posts (socialplanner/post.write) — scheduling Campaign Studio social posts (Social Planner section).
- View Medias (medias.readonly) — showing the client's own images in Campaign Studio (Medias section).
- View Objects Schema (objects/schema.readonly) — listing contact types in the PSA Sync field mapping (Objects section).
- View Blogs (blogs/list.readonly) — choosing which HighLevel blog Campaign Studio saves drafts into (Blogs section).
- Edit Blog Posts (blogs/post.write) — saving a Campaign Studio blog as a HighLevel draft (Blogs section).
- Edit Existing Blog Posts (blogs/post-update.write) — updating that draft when the blog is published again (Blogs section).
- View Blog URL Slugs (blogs/check-slug.readonly) — making sure the post's web address does not clash with another post (Blogs section).
- View Blog Posts (blogs/posts.readonly) — reading the draft back to confirm it landed (Blogs section).
Which accounts and records: Create a Private Integration in the client's own sub-account, not an agency token. Use its matching Location ID and choose a pipeline and stage for leads. For the Portal's OAuth app, complete installation/re-authorization for that same location; the consent screen supplies its enabled scopes. Core contact/opportunity scope failures can block delivery; missing optional custom-field/user scopes skip those extras and do not mean all leads stopped.
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.
ConnectWise CPQ
Required permissions and account access
- CPQ 2022.2 or later: create a dedicated API key and provide its Access Key, Public Key and Private Key.
Which accounts and records: This connection is still in build: credentials are parked and no read or push occurs. Do not mark it active or promise delivery before the connector ships.
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.
ConnectWise PSA
1-way — read only
Required permissions and account access
- Set Inquire Level to All on Companies → Company Maintenance, Companies → Contacts and Sales → Opportunity — and, if you use Client Upsell, on Finance → Agreements, Service Desk → Service Tickets and Time & Expense → Time Entry. Recommended for warranty opportunities: also set Companies → Configurations → Inquire Level All. Leave Add, Edit and Delete at None everywhere.
Which accounts and records: Use your existing API member and one key for this system. Inquire Level must be All for every required module, not just companies. The member's company/location restrictions must cover the clients you intend to read. Recommended for warranty opportunities: also enable Companies → Configurations → Inquire Level All, with Add/Edit/Delete at None.
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.
2-way — read and write
Required permissions and account access
- Set Inquire, Add and Edit to All on Companies → Company Maintenance, Companies → Contacts and Sales → Opportunity. If you use Client Upsell, also set Inquire Level to All (only) on Finance → Agreements, Service Desk → Service Tickets and Time & Expense → Time Entry. Recommended for warranty opportunities: also set Companies → Configurations → Inquire Level All, with Add/Edit/Delete None on Configurations. Leave Delete at None everywhere.
Which accounts and records: Use your existing API member and one key for this system. Inquire Level must be All for every required module, not just companies. The member's company/location restrictions must cover the clients you intend to read. Recommended for warranty opportunities: also enable Companies → Configurations → Inquire Level All, with Add/Edit/Delete at None.
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.
Autotask
1-way — read only
Required permissions and account access
- Its security level must be able to view Companies, Contacts and Opportunities — and Contracts and Tickets, if you use Client Upsell — with every add, edit and delete right turned off. Recommended for warranty opportunities: also allow Configuration Items view.
Which accounts and records: Use an API-only resource, with account access covering the companies you intend to read. Recommended for warranty opportunities: also enable view access to Configuration Items. API Tracking Identifier → Integration Vendor must be Marketopia - Lead Machine, or supply the identifier for the vendor actually assigned to this API resource. Generate Key and Secret on that resource.
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.
2-way — read and write
Required permissions and account access
- Its security level must be able to view, add and edit Companies, Contacts and Opportunities (and Notes, if you want notes copied). If you use Client Upsell, it must also be able to view Contracts and Tickets. Recommended for warranty opportunities: also allow Configuration Items view, without add, edit or delete access to Configuration Items. Turn off every delete right.
Which accounts and records: Use an API-only resource, with account access covering the companies you intend to read. Recommended for warranty opportunities: also enable view access to Configuration Items. API Tracking Identifier → Integration Vendor must be Marketopia - Lead Machine, or supply the identifier for the vendor actually assigned to this API resource. Generate Key and Secret on that resource.
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.
HaloPSA
1-way — read only
Required permissions and account access
- On the Permissions tab, tick only permissions that start with read: — for customers, contacts and opportunities, plus read:contracts and read:tickets if you use Client Upsell. Nothing that starts with edit: a HaloPSA key that can edit is refused as 1-way.
Which accounts and records: Use a Client ID and Secret (Services) application, Login Type Agent, bound to an agent who can see the intended customers, contracts and tickets. An application scope cannot override the agent's record restrictions.
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.
2-way — read and write
Required permissions and account access
- On the Permissions tab, tick edit:customers, edit:contacts and edit:opportunities. If you use Client Upsell, also tick read:contracts and read:tickets.
Which accounts and records: Use a Client ID and Secret (Services) application, Login Type Agent, bound to an agent who can see the intended customers, contracts and tickets. An application scope cannot override the agent's record restrictions.
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.
HubSpot
Required permissions and account access
- crm.objects.contacts.read and crm.objects.contacts.write
- crm.objects.companies.read and crm.objects.companies.write
- crm.objects.deals.read and crm.objects.deals.write
- communication_preferences.read and communication_preferences.read_write
Which accounts and records: Create a dedicated Service Key in the client's HubSpot account as a user with the matching CRM access. A working legacy private-app token can stay. Choose the client's deal pipeline and stage; never reuse another integration's key.
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.
Pipedrive
Required permissions and account access
- A personal API token (Personal preferences → API). Pipedrive tokens have no scopes: the token can do whatever its user can, so use a user who can add people, organizations, leads and notes and can see every deal and lead.
Which accounts and records: Use a sales manager's or admin's token from the client's own Pipedrive company, with visibility of all deals and leads. Leads land in the Leads Inbox with an MSProspector label; nothing is deleted.
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.
Kaseya BMS
Required permissions and account access
- A dedicated API user (User Type API-Employee) with its own security role: CRM Accounts, Contacts and Opportunities with View and Modify, no Delete, plus Admin → Special Features → Has API Access. Nothing in Service Desk, Finance or HR.
Which accounts and records: Create the API user in the client's own Kaseya BMS tenant, never someone's own login. Sign-in is the API user's username and password with the company (tenant) name and the region the tenant is hosted in. Choose the prospect account type, the starting opportunity status and which statuses mean won or lost; nothing is deleted.
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.
Syncro PSA
Required permissions and account access
- A second, separate API token (Admin → API → API Tokens → New Token → Custom Permissions) with only Customers - List/Search, Customers - View Detail, Leads - List/Search and Estimates - List/Search. No Assets, Scripts, Policies or any other RMM permission, and no Delete — a token that can see assets is refused.
Which accounts and records: Create the token in the client's own Syncro account, separate from any view-only Client Upsell token. Signals land as Leads, never as customers or contacts; a lead for an existing customer is linked to it and says so. Won is counted only from an estimate approved for that customer after the lead was delivered; nothing is deleted.
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.
Salesforce
Required permissions and account access
- A dedicated integration user (the Salesforce Integration user license fits) whose permission set has API Enabled; Read, Create and Edit on Leads; Read on Accounts, Contacts and Opportunities; and Edit Tasks. No Delete, Modify All Data or View All Data.
Which accounts and records: Create an External Client App (or Connected App) in the client's own Salesforce org with Client Credentials Flow on and Run As set to that integration user, scope api. Paste the org's My Domain address with the consumer key and secret. Leads land with Lead Source MSProspector; Accounts, Contacts and Opportunities are only read, and nothing is deleted.
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.
Datto RMM
Required permissions and account access
- Enable API Access. Give the API user's security level view access to sites, devices, device audit/software and Monitor alerts (Monitor: View). No jobs, scripts or remote control.
Which accounts and records: Assign every intended site to the API user's security level and use the region-specific API URL, API Key and API Secret Key.
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.
NinjaOne
Required permissions and account access
- API Services (machine-to-machine); Client Credentials grant; Monitoring scope only. Management and Control must be unticked.
Which accounts and records: Use the client's NinjaOne region. Ensure the application can see the intended organizations and devices. This connector checks granted scopes and refuses write-capable keys.
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.
Addigy
Required permissions and account access
- View Devices and View Policies only. No command, assignment or MDM permissions. The person creating the token needs View / Create Integrations API Keys.
Which accounts and records: Use a dedicated token with access to the intended client policies and devices. Both device and policy reads must succeed.
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.
Jamf Pro
Required permissions and account access
- Settings → API Roles and Clients: API Role with Read Computers and Read Sites only; API Client bound to that role.
Which accounts and records: Use Jamf Pro (not Jamf School or Protect), its client ID/secret, and the correct instance. Cover every intended site.
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.
ConnectWise Automate
Required permissions and account access
- Dedicated user class that can view clients and computers only; no scripts, commands or remote control.
Which accounts and records: Give the API user access to intended clients and locations. This connector uses username/password and cannot answer an interactive two-factor prompt; follow the dedicated-user setup steps with the client's administrator.
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.
Kaseya VSA
Required permissions and account access
- Dedicated role with view access to machines and organizations only; no scripts, execution or remote control.
Which accounts and records: Assign the intended organizations to the user. Supply that user's personal access token from Access Tokens, not their normal password, and the correct VSA instance.
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.
Syncro
Required permissions and account access
- Custom Permissions: Customers - List/Search, Customers - View Detail, Assets - List/Search, Assets - View Details only.
Which accounts and records: Use a dedicated API token from the client's Syncro instance and cover the intended customers and assets.
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.
Atera
Required permissions and account access
- Use the API Key from Admin → Data management → API. Atera's key cannot be limited to reading; our reading connector has no write path.
Which accounts and records: The key must belong to the account that holds the intended customers and devices. Do not describe the vendor key itself as read-only.
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.
N-able N-central
Required permissions and account access
- Dedicated API-only user with a role that can view customers and devices. No device actions. Generate its JSON Web Token on API Access.
Which accounts and records: Assign Access Groups covering the intended customers. Follow the dedicated API-user sign-in requirements in the setup steps with the client's administrator.
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.
SuperOps
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.
ConnectWise RMM
Required permissions and account access
- platform.company.read and platform.devices.read only.
Which accounts and records: Use the correct ConnectWise platform API client and region, with company access covering intended clients. This is separate from ConnectWise Automate and ConnectWise PSA.
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.
IT Glue
Required permissions and account access
- Administrator creates a dedicated Custom API Key. Leave Password Access unticked. The connector reads organizations, configurations, domains and domain-expiration metadata, never passwords.
Which accounts and records: Use the regional API host (US/EU/Australia), not the human login host. The key must see the intended organizations.
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.
Cloudflare
Required permissions and account access
- Custom API token: Zone → Zone → Read only; Zone Resources → All zones you intend to include.
Which accounts and records: Use the Cloudflare account holding the clients' zones. This adds domain matches to known clients; it does not create new 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.
GoDaddy
Required permissions and account access
- Production API Key and Secret, not an OTE test key. These keys cannot be limited to reading; our connector only reads.
Which accounts and records: Use the account holding the intended domains, with production Domains API eligibility. A successful login does not prove the account is entitled to that API.
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.
IONOS
Required permissions and account access
- API Key Public Prefix and Secret from developer.hosting.ionos.com. The key cannot be limited to reading; our connector only reads.
Which accounts and records: Use the account holding the intended domains. Domains attach only to clients already identified by another source.
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.
Datto BCDR
Required permissions and account access
- Dedicated Partner Portal API key with access to backup devices and asset status. Supply both Public Key and Secret Key.
Which accounts and records: When creating the key, leave the client and vendor restriction boxes empty to cover the partner account's clients. If intentionally restricted, only that scope will be assessed.
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.
Veeam Service Provider Console
Required permissions and account access
- Dedicated Portal ReadOnly Operator / Read-only User account in VSPC Roles & Users. No restore, configuration or other write rights.
Which accounts and records: Use the VSPC instance and DOMAIN\username/password account covering the intended companies and backup jobs; this is not a Veeam Backup & Replication console login.
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.
Axcient x360Recover
Required permissions and account access
- Create a dedicated x360Portal API key from a user who can see the intended clients; use a view-only user where available. The key inherits its creator's rights.
Which accounts and records: Keep the creating user active and authorized for all intended clients. No separate API-key permission picker is used by this connection.
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.
Auvik
Required permissions and account access
- Dedicated user with a read-only role on the intended clients; generate the API Key from that user's profile.
Which accounts and records: Supply that user's email and the API key, using the regional auvikapi host matching their Auvik site.
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.
Ubiquiti UniFi
Required permissions and account access
- Site Manager → Settings → API Keys. Use its read-only API key; no write permission is required by this connector.
Which accounts and records: The creating account must have access to the intended sites/consoles. Confirm sites and network devices are returned.
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.
Proofpoint Essentials
Required permissions and account access
- Dedicated silent user on the partner organization with the Channel Admin role. Proofpoint Essentials read-only roles cannot use this API; the connector itself only reads. Supply that user's credentials, not an unrelated API token.
Which accounts and records: Use the correct regional Essentials API address and the partner user able to see intended customer organizations. The Channel Admin account must cover the intended customers; do not describe its vendor-side rights as read-only.
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.
DNSFilter
Required permissions and account access
- Account Settings → API: dedicated API Key. This key is not scoped to read-only; the connector itself only reads organizations, sites and policies.
Which accounts and records: Use the MSP account covering intended organizations/sites. Do not promise that the vendor key cannot write.
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.
ThreatLocker
Required permissions and account access
- Custom API user role: View Organizations and View Computers only. No policy changes or execution rights.
Which accounts and records: Bind the API user to the top organization, copy its root Organization ID, and use the portalapi host with the same server letter as the client's portal. Record the token expiry.
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.
SentinelOne
Required permissions and account access
- Service User with Scope Account and Role Viewer. Create its API token and record the expiry.
Which accounts and records: Use the client's console host and account scope covering the intended sites. The connector cannot enumerate all token privileges; verify the assigned Viewer role in the console.
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.
Huntress
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.
RocketCyber
Required permissions and account access
- Provider Settings → RocketCyber API: provider Access Token. No separate read-only scope choice is offered by this setup; our connector only reads.
Which accounts and records: Use the correct US/EU API host and keep /v3 in the address. The token must cover the intended customer accounts and agents.
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.
Pax8
Required permissions and account access
- Integrations → API credentials: dedicated Client ID and Client Secret with access to companies and subscriptions. The token response does not let this connector prove read-only privileges.
Which accounts and records: Use the partner account holding the clients' subscriptions. Our reading connector does not change subscriptions.
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.
Sherweb
Required permissions and account access
- Cumulus → Security → APIs: API application's Client ID, Client Secret and Subscription Key; all three are required. The connector reads customers and subscriptions.
Which accounts and records: Use the partner account holding the intended customers. The Subscription Key is separate from the Client Secret; authentication alone does not prove subscription access.
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.
Microsoft 365 / Microsoft Graph
Required permissions and account access
- Application permissions: Organization.Read.All, AuditLog.Read.All and Policy.Read.All.
- Optional Microsoft 365 usage/adoption reports: Reports.Read.All.
- CSP/GDAP discovery: DelegatedAdminRelationship.Read.All.
- Device findings: DeviceManagementManagedDevices.Read.All (Microsoft Graph) and Machine.Read.All under WindowsDefenderATP, not under Graph.
- AI application and outside-administrator findings: Directory.Read.All. All listed permissions read data; no Mail, Files, Send, user-write or device-action rights are needed.
Which accounts and records: Use a multitenant application and grant admin consent in every client tenant. Adding a permission requires consent again in each tenant. Enter the intended tenant IDs or use the partner relationship. MFA assessment also requires Entra ID P1/P2; Defender/Intune assessment requires the corresponding service/license. A tenant that has not consented remains unassessed, not healthy. Record secret expiry.
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.
Microsoft Power Platform
Required permissions and account access
- Use the multitenant Microsoft 365 application (Organization.Read.All; DelegatedAdminRelationship.Read.All for partner discovery).
- In every client tenant an administrator must register it with pac admin application register --application-id <client ID> or New-PowerAppManagementApp -ApplicationId <client ID>.
- This registration is administrator-equivalent; Microsoft offers no granular read-only management-app role. Our connector only reads.
- For run history, add a Dataverse application user in every intended environment with a security role that can READ Process (workflow) and Flow Run.
Which accounts and records: Registration and tenant consent are separate. Cover every intended tenant/environment; an app cannot register itself. Missing Dataverse rights leave run success and usage unassessed.
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.
ScalePad Lifecycle Manager
Required permissions and account access
- A dedicated ScalePad user with Administrator permission must create the API key; ScalePad provides no read-only/scoped key. An active Lifecycle Manager plan is required for its hardware data.
Which accounts and records: Connect the existing key once on Client Upsell → Clients → Push to ScalePad. Reading reuses that key; sending initiatives is a separate action when the MSP clicks Push. Do not create a second read key or describe the vendor key as read-only. Record expiry; deactivating the user revokes access.
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.
Send a signal straight into any of these
One click on a signal creates the company, the contact and the deal. Created once, updated on a re-send, never duplicated — and no invented deal value.
Running something else? The webhook above reaches anything, and the picker in your settings is how we choose which native destination to build next.
Read — powers Client Upsell
34 read-only connectors that power Client Upsell
These are for Client Upsell only — Lead Signals needs none of them. Connect a PSA and the findings start the same day. Add RMM, Microsoft 365 and backup and they compound — each system you connect makes the others more specific, because a seat you bill for in the PSA can finally be checked against a device that exists in the RMM.
PSA
The anchor. Client list, agreements, and ticket metadata — never ticket bodies.
RMM
Device posture: patch state, EDR, OS and hardware age, software EOL.
Microsoft 365
Licenses purchased versus assigned, and MFA registration where consented.
Automations & AI agents
Power Automate flows that stopped running, and Copilot Studio agents open to everyone or needing no sign-in.
Backup
Protected versus unprotected endpoints, and jobs that quietly stopped succeeding.
Security
Who is actually protected: endpoints still onboarding, seats never deployed, sites with no filtering policy.
Network & documentation
Unmanaged devices on a client network, and what the docs say should be there.
Domains
Your clients' web addresses, matched to clients you already have, so email-security and website checks can run.
Distribution
What each client already buys through you — the gap a PSA agreement alone can't see.
Lifecycle
Purchase and warranty dates for each client's hardware, for the ageing-hardware finding. ScalePad keys can't be limited to reading; our reading connection is built to only read, and sending findings to ScalePad happens only when you click Push.
We only ever read
Client Upsell has no code that can change anything in your tools — an automated check on every change to our code blocks any that could. You create a view-only key using our setup steps, and for some tools (HaloPSA and NinjaOne) we also check the key when you save it and refuse one that can make changes. The exception is ScalePad, which only issues Administrator keys: that key can't be view-only, so our reading connection is built to only read, and findings reach ScalePad only when you click Push. No finding reaches a client until a person on your team has read it and ticked it. Your key is encrypted with a master key kept in Microsoft Azure Key Vault, so a copy of our database alone can't unlock what you connected.
How we handle client dataSync — for Growth Machine clients
Your PSA and your marketing system, finally agreeing
Contacts, companies and opportunities stay matched both ways between HaloPSA, ConnectWise or Autotask and The Growth Machine — so marketing stops emailing a contact who left, and sales stops working a company that already signed.
Your PSA wins on identity
Names, companies, titles and opportunity stage are owned by the PSA. The Growth Machine owns marketing consent, because it is what recorded the opt-in.
Nothing is written until you map it
Creating a company needs values that exist only inside your instance. Until a human loads those lists and ticks the mapping complete, writes are blocked outright — never guessed.
Dry run first, and it never deletes
Every sync starts in dry run so you read what would change before anything does. There is no delete path in either direction, by design.
Running both? You create two keys — a view-only one for Client Upsell, and a separate one for the sync that can add and update records. Keeping them apart is why Client Upsell can never change your PSA.
Don't see your platform?
Request an integration
Building a CRM or platform for the MSP space and want to receive MSProspector signals directly? Or are you an MSP whose CRM isn't listed? We're adding integrations every quarter.
Request an integration