Disclosure: We're affiliates of Krafera, the maker of Silent Failure Watch, so we earn a commission if you buy through our links, at no extra cost to you. Krafera also gave us a free copy to review. The opinions are ours.
Reader offer: use code SOLUTIONSCRAFT20 for 20 percent off. Get Silent Failure Watch with 20 percent off.
This Silent Failure Watch review looks at Krafera's creative answer to a quiet n8n problem. A workflow that fails loudly is easy to spot. One that stops running without a word is not: a schedule that never fires raises no error in n8n, so nobody is told. Silent Failure Watch is a pack of nine n8n workflows built to notice exactly that, and this review covers what is in the pack, how it did in our local test lab, what it costs and who it suits.
The short answer: if you run self-hosted n8n 2.x, for yourself or for clients, Silent Failure Watch is a practical, thoughtful way to find out when a workflow quietly stops. It catches workflows that go quiet , emails you once when something goes wrong and once when it recovers , and stays silent when all is well (apart from the Monday report in the Full pack). The Full pack also adds ready-made client handover documents. The entry pack is $12, or about $9.60 with our reader code, so getting Silent Failure Watch with 20 percent off is an easy first step.
Blip: Nothing failed. Nothing ran either. On paper, that is a perfect error record.
What you get in the pack
Nine workflows for your own self-hosted n8n, plus handover documents for client work. Here is what each one does for you.
Did it run is the heart of the pack, and its name is the question it answers. Every 15 minutes it goes through the workflows on your watch list and checks that each one still exists, is switched on, did not fail last time and, if you set a time limit, has run successfully within it. You get one email when something goes wrong and one when it is back to normal , and nothing while nothing changes. It also points out active workflows that have no error workflow set, and it can ping an outside uptime service after every check, so you hear about it even if the watcher itself or your whole server stops.
- Error alert emails you when a workflow fails, with the workflow, the step, the error, the record involved and a link to the run. Repeats are counted instead of flooding your inbox, and you can send each workflow's alerts to its own owner.
- Count check compares yesterday's rows in two places, so a sync that finished without an error but skipped a few orders shows up , along with extras and mismatched values. It ships set up for example tables, so you point it at your own.
- Webhook intake and Webhook reconciliation log each incoming event once, so repeat deliveries are ignored , and each morning it compares your sender's own list with the log and emails you only if events never arrived or were processed twice.
- Process with retry and Retry failed items send items to an API one at a time, so one failing item does not stop the rest. Failed items are tried again, and after five attempts in all you get one email listing what was given up.
- Nightly backup writes a dated backup of all your workflows every night and reads the file back and counts the workflows against n8n, emailing you only if the file cannot be written or the copy does not match. Our post on backing up n8n and testing the restore shows how to check a restore.
- Weekly health email is a Monday report : for each watched workflow, the runs and failures of the last seven days (from each workflow's 250 newest runs), the last success, and any items waiting for a retry or given up. Send it to your client and keep the alerts with you.
The Full pack also includes a one-page monitoring handover for client work , as a blank template and as a filled example, so you can show a client exactly what is watched, who gets which message and who fixes what.
It suits freelancers and agencies running client automations on their own server, and the license covers your own clients. You need self-hosted n8n 2.x with Data tables, an n8n API key that lets the workflows read your workflows and runs, a mail account for the alerts, and n8n set to keep successful runs for longer than your longest time limit. It isn't written for n8n Cloud. We looked at it on its own rather than against other options, so for n8n silent failure monitoring, read this as one detailed look rather than a comparison.
How it did in our Silent Failure Watch review
We tried the Full pack in our own local test lab, with test data only, and looked at four things.
- Nothing hidden inside. We read through all nine workflows and found no hidden addresses, hidden code or stored secrets.
- It keeps to itself. While it ran we watched the network traffic, and the pack contacted nothing beyond the addresses we had set up for it.
- It sets up cleanly. All nine files imported without errors, and the workflows created the data tables they use on the first run.
- Did it run catches quiet failures. This is the check-up workflow described above, so it was the test that mattered most. We ran 26 checks of its alerts (a workflow switched off, failing, deleted or quiet past its time limit, and the email when it recovers), and it passed all 26.
Blip: A monitoring pack that does not phone home. I would shake its hand, if I had one.
Setting it up
The README walks you through setup step by step, including a "try a bad day" drill: switch off one watched workflow, and within 15 minutes an email names it. Switch it back on, and the next email says it is back to normal. It is a satisfying way to see the pack earn its place. Two choices are worth making on day one.
1. Give the pack its own narrow API key. The README names the three read permissions it needs: list workflows, list executions and read executions. A key with just those was enough for the workflows that use it, and it was refused when we tried to create a workflow with it, which is the careful kind of advice you want from a monitoring pack. If a key ever lands somewhere public, our post on leaked n8n API keys covers rotating it.
2. Limit that key to your own n8n address. The README shows how to restrict the API credential to your n8n host, so the pack's web requests cannot send the key anywhere else, and reminds you to check the base URL on the credential itself, because the three workflow-list steps use it as written. With the restriction on and a mistyped address, one of those web requests stopped with "Domain not allowed" instead of sending the key off.
What it costs, and how to save 20 percent
There are three packs, and the reader code covers all of them:
- Single, $12 (about $9.60 with the code): Did it run.
- Core, $39 (about $31.20): Did it run, Count check and Error alert.
- Full, $79 (about $63.20): all nine workflows and the handover folder.
Krafera backs the pack with a 14-day money-back guarantee : if the product does not install or does not work as described, you message Krafera through Gumroad within 14 days of purchase and get a full refund.
Krafera gives our readers the code SOLUTIONSCRAFT20 for 20 percent off every pack, and our link already includes it. If you are weighing Single, Core and Full, get Silent Failure Watch with 20 percent off and compare all three on the product page before you choose.
A few heads-ups for a smooth setup
To keep things smooth:
- On a newer n8n, try it on a copy first. We checked Silent Failure Watch on n8n 2.x. On a newer major version, test it on a copy first. If you run n8n from npm, our guide on moving to Docker before n8n 3.0 helps with that prep.
- Shopify-style sender? Three quick settings. Set the intake's id field as the README table says. Left on the default, a second event about the same order can be skipped as a duplicate without any error message. Signed senders such as Shopify also cannot send Krafera's key header, so add your own signature check in your processing step, as the README describes. For the morning reconciliation, your sender's own list of events must hold the same webhook ids as the Shopify header ids, otherwise it reports false alarms.
- Keep alerts, backups and saved runs private. Error alert hides the secrets it recognizes, but not every format, so keep secrets out of free-text fields and send alerts only to people who may see that data. The backup folder and n8n's saved runs can hold the intake key and any key you pasted straight into a node.
- A few more edge cases. Very large numeric ids are refused, so use a header id or send the id as text. Two copies of an event arriving at the very same instant, or a replay under a new id, can both be processed, so make your processing step safe to repeat. The weekly report reads each workflow's 250 newest runs, so on a very busy workflow older failures are not counted. Krafera's LIMITS file covers the large ids and the same-instant copies; the replay point comes from our own testing.
Our verdict, and where to start
Our verdict. Silent Failure Watch is a creative, thoughtful and practical pack. It tackles a real problem, workflows that stop without any error, it is easy to try at $12, or about $9.60 with our code, and the client handover documents are a lovely touch for anyone who looks after other people's automations. We recommend it to anyone running self-hosted n8n 2.x, especially anyone who skims the heads-ups above and the LIMITS file first.
If you want the simplest win, start with Single: Did it run alone tells you when a workflow quietly stops. Core adds Count check and Error alert. Full adds the webhook, retry, backup and weekly report workflows and the handover documents, which makes it the one for client work. With the 14-day money-back guarantee behind it, get Silent Failure Watch with 20 percent off and pick the pack that fits you. The code SOLUTIONSCRAFT20 is already built into that link.
If you would like more reviews like this one, you will find them alongside our other n8n guides in the automation section.
Disclosure: The product links in this article are affiliate links: if you buy through them, we may earn a commission at no extra cost to you. We agreed to the affiliate arrangement with Krafera before publishing this article, and Krafera gave us a free copy of the Full pack, through a one-use code, to review. Krafera provides the reader code SOLUTIONSCRAFT20, and it does not change what we found. Krafera's README links to three of our guides (the same three we link in this article), because we offered them. That link is in our favour, so we say so. We wrote every word of this article ourselves. Before publishing, we sent Krafera a longer write-up of the limits we found, and Krafera checked it against its current README and limits file and found no factual errors. See our affiliate disclosure for how we handle affiliate links in general.
The SolutionsCraft team
Top comments (0)