Integration

n8n Integration for Domain Alerts

If you run n8n (self-hosted or cloud), Notify.domains plugs in the same way it plugs into Zapier. Create a Webhook node in n8n, paste the URL into your Notify.domains profile, and every domain change fires a workflow. Full payload, optional HMAC verification, no vendor lock-in.

Setup

1

Create a Webhook node in n8n

In your n8n workflow, add a Webhook trigger node. Set the method to POST. Copy the production webhook URL (it looks like https://your-n8n-host/webhook/abc123).
2

Paste into your Notify.domains profile

Open your Profile, scroll to Notifications, paste the n8n URL into Custom webhook URL, and save. Generate a signing secret if you want HMAC-verifiable payloads.
3

Wire downstream nodes

Connect the Webhook node to whatever comes next: HTTP Request to your drop-catcher API, a Slack node, a Postgres insert, a Discord message, or an IF node that branches on event tier. The full payload is available on $json.body.

Example payload

This is exactly what the webhook body looks like. Use it to build your downstream logic.

{
  "event": "domain.alert",
  "version": 1,
  "occurred_at": "2026-04-19T18:30:00Z",
  "domain": "example.com",
  "tier": "act_now",
  "summary": "example.com is in pending delete. Drop expected in 5 days.",
  "dashboard_url": "https://notify.domains/dashboard/domain/example.com",
  "lines": [
    { "label": "Registrar",  "value": "GoDaddy" },
    { "label": "Drop window", "value": "Apr 24, 2026 7:00pm UTC" }
  ]
}

What you get

Self-hosted or cloud

Works with any reachable n8n instance. Run it yourself or use n8n cloud; the integration is identical.

Full payload on the Webhook node

Every field of the event is accessible in your workflow for routing, filtering, and downstream actions.

Branch on tier or summary

Use n8n IF nodes to send act_now events to your drop-catcher automation and fyi events to a spreadsheet.

HMAC verification

Generate a signing secret in Notify.domains. Every payload gets an X-Notify-Domains-Signature: sha256=... header your workflow can verify with a Function node.

Frequently asked questions

Does n8n need to be publicly reachable?

Yes. Notify.domains POSTs events to a public URL, so the n8n Webhook node has to be reachable from the internet. If n8n is on a private network, put it behind a reverse proxy, tunnel (ngrok, Cloudflare Tunnel), or use n8n cloud.

Can I trigger different workflows for different events?

One workflow, branched inside n8n. The webhook URL is account-wide, so all events hit the same trigger node. Use an IF or Switch node to branch on $json.body.event or $json.body.tier into separate sub-flows.

What authentication does the webhook use?

If you set a signing secret in your Notify.domains profile, every payload includes an X-Notify-Domains-Signature header of the form sha256=<hex>. Compute HMAC-SHA256(body, secret) on your side and compare. Unsigned payloads are also supported if you leave the secret blank.

n8n Integration for Domain Alerts

Setup

Create a Webhook node in n8n

Paste into your Notify.domains profile

Wire downstream nodes