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.
Send NorthDuty Alerts to Make (formerly Integromat)
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, 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.
What teams automate with NorthDuty + Make
Start with one scenario and a router — these four branches cover most needs.
Client-facing incident reports
Append alerts to a per-client Google Sheet or Airtable base and feed monthly 'what we caught' reports — proof of value for maintenance retainers.
Tickets and tasks
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.
Multi-channel escalation
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.
Why pair monitoring with Make
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.
Why use the webhook instead of chat-only alerts
A scenario can act on alert data; a chat message can only be read.
- One-URL setup — works on Make's free plan
- Structured JSON: filter and route on severity, rule type, or project
- Covers every alert rule — health, response time, journeys, SSL and domain expiry
- Fan one alert out to logging, tickets, and notifications in a single scenario
- Nothing to host, no code to maintain
How to connect NorthDuty to Make
A custom webhook module is the whole integration.
1
Create a scenario with a custom webhook
In Make, create a scenario, add the 'Webhooks' → 'Custom webhook' module, create a new webhook, and copy the URL Make generates.
2
Add a custom webhook channel in NorthDuty
In your NorthDuty project's notification channels, add a Custom Webhook channel and paste the Make URL as the destination.
3
Route alert rules to the channel
Point journey failures, downtime, and any other rules you want automated at the new channel.
4
Determine the data structure and build
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.
Related NorthDuty Pages
Explore pricing, feature details, solution pages, and related tools connected to this website monitoring use case.
Pricing
Pricing
NorthDuty plans are sized by how many checkout, signup and login journeys you monitor: Free, $29 Starter, $79 Pro, $199 Business. 7-day trial, no card.
Compare pricing plansHub
Features
Explore NorthDuty features: coverage-aware AI journeys, a cross-site workspace overview, website health checks, and connected incident response.
Browse FeaturesHub
Solutions
Explore NorthDuty solutions for ecommerce website monitoring, SaaS website monitoring, agency website monitoring, and startup website monitoring.
Browse SolutionsFeature
Integrations
Route NorthDuty alerts to the channels your team uses: email, Slack, Microsoft Teams, Discord, Google Chat, custom webhooks, Telegram, SMS, and WhatsApp.
Explore IntegrationsFeature
Zapier Integration
Connect NorthDuty alerts to Zapier in about two minutes with a webhook: log incidents to Google Sheets, open Jira or Trello tickets, trigger 8,000+ apps.
Explore Zapier IntegrationFeature
n8n Integration
Trigger n8n workflows from NorthDuty alerts with a webhook node: self-hosted or cloud, full alert JSON, no code. Built for agencies running their own stack.
Explore n8n IntegrationFeature
Alerting
Send NorthDuty alerts to email, Slack, Teams, Discord, Google Chat, webhooks, Telegram, WhatsApp, and SMS.
Explore AlertingFrequently Asked Questions
Answers to common questions about this monitoring feature and when teams should use it.
Does NorthDuty have a native Make app?
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.
Does this work on Make's free plan?
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.
What data arrives in the webhook?
JSON with the alert title, rule and ruleLabel, severity, project (id, name, baseUrl), threshold, observedValue, unit, comparator, dashboardUrl, and a plain-language message.
Can I route different clients' alerts differently?
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.
Start monitoring your website with NorthDuty today.
Connect NorthDuty to Make and let scenarios handle the triage — routing, logging, and escalating every monitoring alert.
7 days with Pro features and limits, no credit card — then keep one daily journey on the free plan.