Connect HaloPSA
Sync clients, sites, users and assets from HaloPSA.
This guide connects HaloPSA so Knowpoint can read your clients, sites, users and assets. Knowpoint only reads from Halo. It never changes anything there.
1. Create an API application in Halo
- In Halo, go to Configuration → Integrations → HaloPSA API → View Applications and choose New.
- Name it, for example Knowpoint, and choose the authentication method Client ID and Secret (Services).
- Set the login type to Agent and choose an agent the integration acts as.
- Under Permissions, allow read:customers and read:assets.
- Save, and copy the Client ID and Client Secret.
2. Connect in Knowpoint
Go to Admin → PSA & RMM sync → HaloPSA and fill in:
| Field | What to enter |
|---|---|
| Halo address | The address you use for Halo, such as https://yourcompany.halopsa.com |
| Tenant | Only for hosted Halo, if Halo gave you a tenant name. Otherwise leave it empty. |
| Client ID / Client secret | From step 1 |
Choose Save and continue, then Test connection.
What's synced
| From Halo | Into Knowpoint |
|---|---|
| Clients (active) | Organizations |
| Sites | Locations, with address and phone |
| Users | Contacts, with job title, email, phone and mobile. Halo's placeholder General User is skipped. |
| Assets (active) | Assets, by asset type, with serial number and warranty where Halo has them |
Troubleshooting
| Message | What to do |
|---|---|
| Halo (sign in) returned HTTP 401 | The client ID or secret is wrong, or the application is inactive. |
| HTTP 403 | The application is missing the read:customers or read:assets permission. |
| Can't find … | Check the Halo address. It should start with https://. |
See PSA & RMM sync for matching companies, scheduling and what a sync changes.
Tip: Halo can also receive tickets from Knowpoint alerts. That's set up separately, as an alert channel.
Didn't find what you needed? Email us about this page