- A webhook that receives no more calls generates no error on the automation side.
- The cause is almost always on the sender's side.
- The only reliable detection is the absence of executions over an abnormal period.
- Set a silence delay per webhook, based on its usual traffic.
A webhook-triggered workflow waits to be called. If nobody calls it, nothing happens, and “nothing” is not an error. It is the most widespread form of silent failure.
The seven most common causes
- The URL changed. The workflow was duplicated, the webhook recreated, or the instance moved to a new domain. The sender still calls the old address.
- The test URL instead of the production URL. In n8n, the test address only answers while the editor is listening.
- The form was rebuilt. New theme, new plugin: sending to the webhook was never reconfigured.
- The sender disabled the webhook. Many services suspend a webhook after several error responses.
- A firewall or proxy blocks the calls. A rule change, an allow-list, bot protection.
- The TLS certificate expired. The sender refuses to connect.
- The workflow is inactive. Deactivated by hand or by the platform.
Why you do not see it
In six cases out of seven, the call never reaches your automation. So there is no execution, no failure, no alert. The history simply shows a last successful execution that keeps getting older.
The detection method
It comes down to one rule: for each webhook, define the normal maximum time between two calls, and alert when it is exceeded. A contact form that gets ten enquiries per working day should not stay mute for twenty-four hours on a weekday. A shop taking orders every hour should not stay mute for half a day.
Two precautions: allow for quiet days, and do not confuse “no calls” with “could not read the history”.
Automating the check
Nokto works out this delay from each workflow's history and opens a “silent” incident as soon as it is exceeded. Try it on your webhooks for 14 days.
Frequently asked questions
How do I test that a webhook still works?
Send a test request to the production URL and check that an execution appears in the history. Do it after every change to the form or the sending site.