PSA integration
HaloPSA clients, tickets, and contracts lined up alongside every other system your team works in.
What Vectis syncs
The read side of the adapter. Pulled on a schedule and available everywhere the customer account surface lives.
Actions Vectis can take
Write-back methods this adapter exposes. Rules can call them; so can inline actions on the customer hub. Every action is logged to the audit trail.
How it correlates
Vectis is about HaloPSA joining your other systems around the customer account — not a standalone dashboard. Two concrete examples:
HaloPSA's ticket create requires a ticket type ID and install-specific status + priority IDs. Vectis stores those as workspace defaults so rule authors pick the trigger — not the picklist IDs.
Halo ticket actions, RMM alerts, Datto backup outcomes, and distributor license events merge into one chronological stream per customer. Scroll back a month without losing context.
Setup snapshot
In HaloPSA, go to Config → Integrations → HaloPSA API and create a client-credentials application. Copy the tenant URL you log in at, the Client ID, and the Client Secret (shown only once) into Vectis. Leave scope blank unless your admin has narrowed the default. The first sync pulls clients, tickets, and contracts; subsequent syncs are incremental.
Full setup guideavailable after signup
14-day free trial. Connect HaloPSA at signup. See every customer with their full context on day one. Cancel anytime during the trial at no charge.