Domain Health Hub alerts in your PSA
When a client's domain needs attention, raise a ticket where your team already works. Each recipe is an n8n workflow you import and run on your own n8n: it checks the alert really came from us, then raises a ticket or adds a note to the one already open.
Pick your PSA
- HaloPSAA ticket per problem and domain, with repeats added as private notes.
- AutotaskTickets through the Autotask REST API, with notes for repeats.
- ConnectWise PSAService tickets on the board you choose, with internal notes for repeats.
- SyncroTickets for the right customer, with hidden comments for repeats.
How the recipes work
- Domain Health Hub sends each alert to your n8n webhook as signed JSON: grade dropped, DNS changed, a domain or certificate expiring, a blacklisting, a jump in DMARC failures.
- n8n checks the signature with your webhook's secret and refuses anything unsigned, altered or more than five minutes old.
- It looks for an open ticket for the same problem on the same domain. If there is one, it adds a note; if not, it raises a ticket for the right client.
- It only answers us once the ticket or note is saved, so if your PSA is down we retry for six hours instead of losing the alert.
The signature
Every webhook carries X-DHH-Timestamp (Unix seconds) and X-DHH-Signature: sha256= and the hex HMAC-SHA256 of the timestamp, a full stop and the raw body, made with the signing secret shown once when you add the webhook. The recipes check it with n8n's own Crypto node, against the exact bytes we sent, and keep the secret in an n8n credential.
Using something other than n8n? The same check works anywhere that can read the raw request body. The app shows the payload and headers under Alerts, next to your webhooks. More on alerts.
Recipes, not native integrations
- You run them on your own n8n, which must be reachable over HTTPS at a public address: we only send webhooks to
https://URLs. - They only send alerts one way, into the PSA. Closing a ticket doesn't change anything in Domain Health Hub.
- We built each one from the PSA's published API documentation and ran it end to end in n8n against a stand-in for that API. We haven't run them against live PSA accounts, so try each on a test client first.
- Your PSA vendor may change its API. The workflows are plain n8n nodes, so you can see and change every call they make.
Watch every client domain, every day.
Start a free 28-day trial: up to 3 domains, no card needed.