Connect HaloPSA
HaloPSA is a PSA system for IT service providers. DomainWarn creates tickets for incidents there and takes over the clients from Halo as customers. The integration is in beta: it follows the official Halo API but is new. Check the first tickets and mappings, and let us know if anything looks off. It is included from the Agency plan.
In Halo, under Configuration › Integrations › Halo API, create a new application: authentication “Client ID and Secret (Services)”, login type agent with an agent who may create tickets and read clients, permission “all”. “API Details” shows the resource server, the authorisation server and – for instances hosted by Halo – the tenant.
In DomainWarn, under Settings › Integrations › HaloPSA, enter the Halo URL (without /api), client ID and client secret, plus the tenant if Halo shows one, and the authorisation server only if it is not Halo URL + /auth. When you save, DomainWarn fetches a token and reads the statuses; only then is the connection established. The secret is stored encrypted and never shown.
Tickets in HaloPSA
Choose the ticket type, the priority per DomainWarn severity and – if you like – the status of new tickets and the status when resolved. Follow-ups are added as an action only agents see (no email to the customer).
Then switch on tickets under “Features” and add a “HaloPSA” channel under notifications; like every channel it has a minimum severity and follows the notification rules. A new incident opens a ticket at the company of the customer the domain belongs to; for domains without a mapped customer the chosen default company applies, without one no ticket is created. There is exactly one ticket per incident, even if an alert is repeated or several incidents arrive together. The test send checks the connection and the choices without creating a ticket.
See also: Notification channels · Customers
Map companies from HaloPSA
Under “Companies and customers” you see every active company from HaloPSA. Map it to an existing DomainWarn customer; that always works, because tickets need the mapping. With the “Import customers” feature you can also create companies as new customers – one by one or with “Create all unmapped as customers”. If a customer with exactly that name already exists, it is mapped instead of created twice. Nothing is ever deleted, neither in DomainWarn nor in HaloPSA.
After moving to a smaller plan or with tickets switched off, no new tickets are created; existing ones keep receiving notes and are closed when resolved. “Disconnect” deletes credentials, mappings and ticket references; customers in DomainWarn and tickets in HaloPSA stay.