NorthDuty for n8n: Trigger Workflows on Monitoring Alerts

The NorthDuty integration is built and maintained by NorthDuty and verified by n8n. It starts a workflow the moment NorthDuty raises an alert — a failed checkout journey, downtime, an expiring SSL certificate — and lets any workflow or AI agent read your alerts and sites. Add it from n8n's Nodes panel, paste a NorthDuty API token, and the trigger registers and removes its own webhook. Prefer a generic connection? A plain Webhook node works too.

Start your 7-day trial — no credit card, free plan after.

Use the verified NorthDuty integration to trigger n8n workflows on new alerts or let AI agents read your monitoring data.

What the NorthDuty node does

One package, two nodes: a trigger for new alerts and an action node for reading data.

NorthDuty Trigger: on new alert

Pick a site and, optionally, only critical alerts or specific alert types — user journey failure, health score, response time, SSL expiry, domain expiry, security score. The trigger registers its webhook with NorthDuty when the workflow is activated and removes it when deactivated.

Read alerts and sites

The NorthDuty node's Alert → Get Many and Project → Get Many operations pull recent alerts (filtered by site) and the list of monitored sites into any workflow — for daily digests, client reports, or syncing to your own database.

A tool for AI agents

Attach the NorthDuty node to n8n's AI Agent as a tool and ask questions like 'what broke on my client sites this week?' — the agent fetches live alerts and answers from real monitoring data.

Agency client routing

Branch on the project name or base URL so each client's alerts reach that client's channel, ticket queue, or maintenance-report sheet — one workflow for the whole roster.

Why n8n users monitor with NorthDuty

Teams that self-host n8n like owning their automation: no per-task pricing, full control over data, workflows in version control. NorthDuty fits the same philosophy from the monitoring side — it runs your checkout, signup, login and form journeys in a real browser and checks uptime, SSL and site health from the outside, with nothing installed on the sites, then hands automation-ready data to whatever you run.

With the verified integration, an alert lands as regular workflow data: filter on severity or alert type in the trigger itself, or branch later with IF and Switch nodes, and from there any of n8n's nodes take over — tickets, databases, chat, SMS, or an HTTP request to your own systems. Each alert carries the title, rule type and label, severity, project id, name and base URL, threshold and observed value with unit and comparator, a dashboard link, and a readable message.

Why use the verified integration

Less wiring than a raw webhook, and data you can pull as well as receive.

How to connect NorthDuty to n8n

Four steps, about five minutes.

1

Add the verified NorthDuty integration

In n8n, open the Nodes panel and search for NorthDuty. An instance owner may need to complete the one-time verified-node setup first; after that, everyone on the instance can add NorthDuty or NorthDuty Trigger to a workflow.

NorthDuty in the n8n integration directory

2

Create a NorthDuty API token

In NorthDuty, open Profile → API tokens and create a token (it starts with ndk_). In n8n, add a NorthDuty node, click Connect to NorthDuty, paste the token, and save — n8n tests the connection for you.

3

Add the NorthDuty Trigger

Create a workflow, add NorthDuty Trigger → On new alert, pick the site, and optionally narrow it to critical alerts or specific alert types. Use NorthDuty's Send test button on the site's webhook destination to see a sample alert arrive — leave the filters empty for that, since the test alert has its own type.

4

Act on the alert and activate

Connect the nodes you need — Slack, Jira, Google Sheets, an HTTP request — map fields like project name, rule label and dashboard link, then activate the workflow.

Source code and examples on GitHub

Related NorthDuty Pages

Explore pricing, feature details, solution pages, and related tools connected to this website monitoring use case.

Frequently Asked Questions

Answers to common questions about this monitoring feature and when teams should use it.

Is NorthDuty a verified n8n integration?

Yes. NorthDuty is listed in n8n's integration directory and verified by n8n. The n8n-nodes-northduty package includes NorthDuty Trigger (on new alert) and the NorthDuty node (get alerts, get projects). It is free, MIT-licensed, and has no runtime dependencies.

Can I install it on n8n Cloud?

Yes. NorthDuty is live as a verified integration and appears in n8n's Nodes panel. An instance owner may need to complete the one-time verified-node setup before other users can add it to workflows.

Does it work with self-hosted n8n?

Yes. An instance owner can install the verified node for the instance. For the trigger, NorthDuty must be able to reach your n8n instance over HTTPS, because webhook destinations only accept https URLs.

Which NorthDuty plan do I need?

Reading alerts and sites with the NorthDuty node works with an API token on any plan, including Free. The NorthDuty Trigger delivers alerts through a webhook destination, which needs a paid plan.

Can I still use a plain Webhook node instead?

Yes. Create a Webhook trigger in n8n (method POST), add a Custom Webhook channel in your NorthDuty project's alert settings, and paste the n8n URL. You receive the same alert JSON; the verified NorthDuty Trigger sets this up for you and adds filtering.

Start monitoring your website with NorthDuty today.

Install the NorthDuty node in n8n and keep monitoring, triage, and remediation in workflows you own.

7 days with Pro features and limits, no credit card — then keep one daily journey on the free plan.