Domain Health Hub alerts as Autotask tickets

What it does

1. Domain Health Hub posts an alert to the workflow's webhook in n8n.
2. n8n checks the X-DHH-Signature header against the raw body with your signing secret, and refuses anything unsigned, altered or more than five minutes old (it answers 401).
3. It looks in Autotask for an open ticket titled for the same alert and domain, such as DHH: DNS changed on client.co.uk.
4. If there is one, it adds a note with the new alert. If not, it raises a ticket for the client, with what changed, when, and a link back to the domain in Domain Health Hub.
5. Only then does it answer us. If Autotask can't be reached, n8n answers with an error and we retry after 1, 5 and 30 minutes, then 2 and 6 hours.

n8n has no built-in Autotask node. Community nodes exist; we haven't tested them, so the recipe uses HTTP Request nodes against the Autotask REST API.

Before you start

• n8n reachable over HTTPS at a public address. We only send webhooks to https:// URLs.
• A recent n8n: the signature check uses the Crypto node's HMAC with a Crypto credential, added to n8n in 2026. We tested on n8n 2.42.4. On an older n8n, swap in version 1 of the Crypto node and paste the secret into its Secret field instead.
• Admin access to Autotask, to create the API credentials below.
• An owner login for your Domain Health Hub workspace, to add the webhook.

Set it up

1. Download dhh-alerts-autotask.json and, in n8n, choose Import from file on a new workflow.
2. In Domain Health Hub, go to Alerts, add a webhook with the workflow's Production URL (from its DHH alert node), and copy the signing secret it shows you. It's shown once.
3. In n8n, open the HMAC-SHA256 node, create a Crypto credential and paste the secret into Hmac Secret.
4. For the Find open ticket, Add note and Create ticket nodes: In Autotask, create an API user (API-only security level) and note its username, secret and the tracking identifier (integration code). In n8n, create a Custom Auth credential holding {"headers": {"ApiIntegrationCode": "…", "UserName": "…", "Secret": "…"}}.
5. Open the Ticket details node and fill in the settings at the top (below).
6. Activate the workflow. In Domain Health Hub, choose Send test event on the webhook: a ticket called DHH: Test alert should appear in Autotask for your default client. Close it once you've seen it.

Settings

At the top of the Ticket details node. Client names are matched exactly as they appear in Domain Health Hub; anything unmapped goes to the default.

The Autotask API calls it makes

What it can't do

• It's an n8n recipe, not a native integration: you run it, on your n8n, and we don't support changes you make to it.
• It only works one way. Closing the ticket in Autotask doesn't change anything in Domain Health Hub, and a problem that clears doesn't close the ticket.
• We ran it end to end in n8n against a stand-in for the Autotask API, built from the documentation below. We haven't run it against a live Autotask account, so try it on a test client first.
• If the ticket is saved but our request times out before n8n answers, we send the alert again, and you'll get a note on the same ticket rather than a new one.
• Picklist values (priority, status, note type) differ between Autotask instances: check yours before switching the workflow on.
• Autotask's REST API has a per-hour request limit shared by every integration on your account; each alert uses two calls.

Sources

Each Autotask call was checked against the vendor's documentation:

• Autotask REST API: Tickets
• Autotask REST API: TicketNotes
• Autotask REST API: query calls
• Autotask REST API: creating child entities
• Autotask REST API: authentication headers and zones

And the n8n nodes it uses:

• n8n: Webhook node (Raw Body option)
• n8n: Crypto node (HMAC)
• n8n: Respond to Webhook node
• n8n: HTTP Request credentials

Other PSAs: see every recipe.