PSA integration
ActiScan for HaloPSA
A domain that starts failing a check opens a HaloPSA ticket under the right client, using the ticket type your workflow already expects.
DMARC failing on northfield-cpa.com
NewThe DMARC check started failing on the latest scan. ActiScan's description of the finding is in the ticket.
- Client
- Northfield CPA
- Ticket type
- Security alert (your choice)
Opened automatically by ActiScan
Setup
How it works
- 1
Register an API application
In your HaloPSA instance, create an API application to get a Client ID and secret, plus your instance's Resource Server and Authorization Server URLs.
- 2
Connect
Enter those in Settings with the ticket type new tickets should use. Halo ticket types can make other fields (Impact, Urgency, Category) required, so pick one your workflow supports.
- 3
Match your clients
ActiScan matches your client groups to HaloPSA clients by website domain, automatically where it can, with a picker for the rest.
- 4
Tickets open themselves
A domain that starts failing a check opens a ticket under the right client, as the ticket type you chose.
Questions
What ticket fields does ActiScan set?+
The summary, a description of the finding, the matched client, and the ticket type you chose when connecting.
What if my ticket type requires other fields, like Impact or Category?+
Pick a ticket type that doesn't require fields beyond the ones ActiScan sets. If a required field is missing, that ticket can't be created. Contact us if you need help finding the right type.
Does every client group need to be mapped?+
Only groups you want ticketed need a primary domain and a matched HaloPSA client.
Connect HaloPSA in your dashboard
Connect it once in Settings. Free for 30 days, with no sales call.