HaloPSA Notifications: DNS Alerts That Land as Tickets
If your service desk lives in HaloPSA, your DNS alerts should too. Email and Slack are fine for a heads-up, but the work actually gets tracked, assigned, and closed in your PSA.
ZoneWatcher now speaks HaloPSA directly. Add it as a notification channel and every DNS event we detect becomes a ticket in your instance.
How It Works
When a monitored event fires — a zone change, an approaching expiration, a new blocklisting, a certificate about to lapse — ZoneWatcher builds a ticket and posts it straight into HaloPSA over its REST API.
Under the hood it is a clean OAuth2 client-credentials flow. ZoneWatcher authenticates against your instance’s /auth/token endpoint with the client ID and secret you provide, caches the resulting token until just before it expires, and reuses it across a burst of alerts so we are not re-authenticating on every ticket. If a token ever comes back rejected, we transparently fetch a fresh one and retry.
Each event then becomes a single POST to /api/Tickets carrying a summary, a details body, and — this is the useful part — a priority.
Severity Maps to Your Priorities
Every ZoneWatcher notification carries a severity: critical, high, medium, or low. A zone expiring is critical. A certificate expiring soon is high. A routine record change is medium. A newly discovered zone is low.
When you set up the channel, you map each of those four severities to a priority in your own HaloPSA instance. A critical zone expiration can open a P1; a low-severity discovery can file a P4. ZoneWatcher reads your priority list, ticket types, teams, and clients live from your instance during setup, so you are picking from real values — not typing IDs by hand.
One Event, One Ticket
The integration is deliberately simple: every qualifying event opens its own ticket, tagged with the right type, team, priority, and — optionally — a default client. That keeps it predictable and gives your techs a clean, self-contained work item for each thing that happens in DNS: the domain, what changed, when, and a link back into ZoneWatcher for the full detail.
And if your instance stops accepting tickets — bad credentials, revoked API access — ZoneWatcher notices. After a handful of consecutive failures it automatically disables the channel and alerts your team, so a misconfigured PSA never silently swallows your alerts.
Built for MSPs
If you are a managed service provider watching DNS across dozens of client domains, this closes the loop. Detection happens in ZoneWatcher; the ticket, the assignment, and the SLA clock happen where your team already works.
Connect your HaloPSA instance and let your DNS alerts land as tickets.