Incident routing with filters
One webhook feeds a router: critical alerts page someone, warnings log quietly, and each client's alerts reach that client's tools — all filtered on payload fields.
Make scenarios start from a custom webhook — and NorthDuty's custom webhook channel posts structured alert JSON to any URL. Paste one URL and every monitoring signal — downtime, failed checkout journeys, visual changes, SSL expiry — can start a scenario across the 2,000+ apps Make connects. Webhooks work on Make's free plan.
Start your 7-day trial — no credit card, free plan after.
Turn monitoring alerts into Make scenarios with one webhook URL.
Start with one scenario and a router — these four branches cover most needs.
One webhook feeds a router: critical alerts page someone, warnings log quietly, and each client's alerts reach that client's tools — all filtered on payload fields.
Append alerts to a per-client Google Sheet or Airtable base and feed monthly 'what we caught' reports — proof of value for maintenance retainers.
Create items in ClickUp, Monday, Jira, or Trello when a journey fails, with the failing rule, observed value, and dashboard link mapped into the task.
Chain actions in one scenario: log the alert, notify the team, and if severity is critical, follow up by SMS or phone through Make's telephony apps.
Make's visual scenario builder is popular with exactly the teams NorthDuty serves — agencies and lean SaaS teams that automate operations without a dev team. Adding monitoring alerts as a scenario trigger closes the loop: the same platform that runs your client onboarding and reporting can now react when a client's site breaks.
Because the payload is structured JSON, Make's router and filters can do the triage: severity 'critical' takes the escalation route, journey failures open tickets, and each project's alerts can flow to that client's folder, sheet, or channel. The payload carries the alert 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.
A scenario can act on alert data; a chat message can only be read.
A custom webhook module is the whole integration.
In Make, create a scenario, add the 'Webhooks' → 'Custom webhook' module, create a new webhook, and copy the URL Make generates.
In your NorthDuty project's notification channels, add a Custom Webhook channel and paste the Make URL as the destination.
Point journey failures, downtime, visual changes, and any other rules you want automated at the new channel.
Trigger a test alert so Make captures the payload structure, then build your scenario — add a router, filters on severity or rule, and the action modules you need.
Explore pricing, feature details, solution pages, and related tools connected to this website monitoring use case.
Pricing
NorthDuty plans are sized by how many checkout, signup, and login journeys you monitor: Free (1 daily journey), $29 Starter, $79 Pro, $199 Business, $499 Enterprise. 7-day full trial, no card.
Compare pricing plansHub
Explore NorthDuty features: website health checks every 5 minutes, screenshot-based visual change detection, and AI-suggested user journey monitoring in one project.
Browse FeaturesHub
Explore NorthDuty solutions for ecommerce website monitoring, SaaS website monitoring, agency website monitoring, and startup website monitoring.
Browse SolutionsFeature
Route NorthDuty alerts to the channels your team uses: email, Slack, Microsoft Teams, Discord, Google Chat, custom webhooks, Telegram, SMS, and WhatsApp.
Explore IntegrationsFeature
Connect NorthDuty monitoring alerts to Zapier in about two minutes with a custom webhook: log incidents to Google Sheets, open Jira or Trello tickets, and trigger workflows in 8,000+ apps.
Explore Zapier IntegrationFeature
Trigger n8n workflows from NorthDuty monitoring alerts with a webhook node: self-hosted or cloud, full alert JSON, no code. A natural fit for agencies running their own automation stack.
Explore n8n IntegrationFeature
Send NorthDuty alerts to email, Slack, Teams, Discord, Google Chat, webhooks, Telegram, WhatsApp, and SMS.
Explore AlertingAnswers to common questions about this monitoring feature and when teams should use it.
A listed Make app is on the roadmap. Today the connection runs through NorthDuty's custom webhook channel and Make's Custom webhook module, which carries the full alert payload and sets up in minutes.
Yes. Custom webhooks are available on Make's free tier, so the NorthDuty side (any paid NorthDuty plan for webhook channels) is the only paid requirement.
JSON with the alert title, rule and ruleLabel, severity, project (id, name, baseUrl), threshold, observedValue, unit, comparator, dashboardUrl, and a plain-language message.
Yes. The payload includes the project name and base URL, so a Make router can send each client's alerts to that client's sheet, channel, or ticket queue — or use separate webhook channels per project.
Connect NorthDuty to Make and let scenarios handle the triage — routing, logging, and escalating every monitoring alert.
7 days with every feature unlocked, no credit card required — then keep monitoring on the free forever plan.