How it works
Why monitor
A broken webhook can hide replies, acceptances, or useful job statuses.
n8n recipe
Detect broken webhooks before losing sales signals.
This recipe runs a scheduled webhook health check and fails visibly when an endpoint needs intervention.
What the workflow covers
Nodes and logic
This page describes the recipe publicly; importable JSON files remain protected by API access.
Schedule
Check webhooks several times a day.
Every 6 hours by default.
Health
Read unhealthy, disabled, and failure counters.
Keep affected URLs.
Alert
Fail the workflow if human action is needed.
Connect failure to Slack or email in n8n.
Verified facts
What the tool should clarify before being used.
Use caseBased on the internal `webhook-health-monitor.workflow.json` example.
Expected outputCheck every 6 hours.
Method proofEvery 6 hours by default.
Verification method
How to turn the template into an actionable step.
- 01 Schedule Every 6 hours by default.
- 02 Health Keep affected URLs.
- 03 Alert Connect failure to Slack or email in n8n.
How it works
Ops ownership
Every alert needs an owner and clear correction action.
