Send NorthDuty Alerts to Zapier

In Zapier, create a new Zap and choose 'Webhooks by Zapier' → 'Catch Hook' as the trigger. Zapier shows a unique webhook URL — copy it.

In your NorthDuty project, open notification channels, add a Custom Webhook channel, and paste the Zapier URL as the destination.

Point the alert rules you care about — journey failures, downtime, visual changes, SSL expiry — at the new channel, alongside any existing email or Slack routing.

Trigger a test alert so Zapier catches a sample payload, then map fields like title, severity, project name, and dashboardUrl into your action steps and turn the Zap on.

Does NorthDuty have a native Zapier app?

A native Zapier app with built-in triggers is on the roadmap. Today the connection runs through NorthDuty's custom webhook channel and Zapier's Catch Hook trigger, which takes about two minutes to set up and carries the full alert payload.

What data does the webhook send?

A JSON object with the alert title, rule and ruleLabel, severity, project (id, name, baseUrl), threshold, observedValue, unit, comparator, a dashboardUrl link, and a plain-language message — everything a Zap needs to filter, branch, and act.

Which plans support this?

Custom webhook channels are available on any paid NorthDuty plan (email alerts are on every plan, including Free). On the Zapier side, 'Webhooks by Zapier' is a premium trigger, so it requires a paid Zapier plan.

Which alerts can trigger a Zap?

Any alert rule in the project: health score, response time, failed user journeys, visual differences, SSL expiry, API monitor failures, security score, and domain expiry. Route all of them or only some to the webhook channel.

Can I send different alerts to different Zaps?

Yes. Add multiple custom webhook channels — one per Catch Hook URL — and route different alert rules to each, or catch everything in one Zap and use Zapier filters and paths to branch.