PSA
HaloPSA integration
Use HaloPSA? Connect it to MSProspector to get new leads delivered into it, find upsell revenue in your clients and sync it with your marketing.
Reads your client list, agreements and ticket subjects (never the ticket text) to find what each client is missing. View-only.
Setup steps are for connected customers — sign in to read them.
What we find in HaloPSA
Clients, agreements, ticket themes, seat drift.
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 HaloPSA connection does
Read — powers Client Upsell
Read your clients' stack
The anchor. Client list, agreements, and ticket metadata — never ticket bodies.
Deliver — powers Lead Signals
Receive new Lead Signals
Each signal you send becomes a company, contact and deal — created once, updated on a re-send, never duplicated. No amount is written: we don't know the deal's value and won't put a made-up number in your forecast.
Sync — for Growth Machine clients
Two-way sync with The Growth Machine
Contacts, companies and opportunities stay matched both ways. Your PSA owns names and companies; The Growth Machine owns phone numbers and always owns marketing consent. It starts with a preview run, and it never deletes a field. It uses the same key you connect here — set to 2-way — so you only enter it once.
Permissions to prepare with your administrator
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.
HaloPSA integration — common questions
- How does the HaloPSA integration help my MSP get more leads and sales?
- Lead Signals finds companies in your territory showing signs they need an MSP, and delivers each one into HaloPSA as a lead with a note saying why now — so your team calls while it's warm, without leaving HaloPSA. Client Upsell reads HaloPSA 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. Contacts, companies and opportunities in HaloPSA stay matched with The Growth Machine, so your marketing campaigns and your sales pipeline work from the same records.
- What does the HaloPSA integration read?
- Reads your client list, agreements and ticket subjects (never the ticket text) to find what each client is missing. View-only.
- What does MSProspector find in HaloPSA?
- Clients, agreements, ticket themes, seat drift.
