The branch that skips
step SKIPPED · run COMPLETEDA condition that can no longer match doesn't error — it skips, and the run still reports success. One instance was found carrying 27 of them.
Monitoring for n8n & Make
Your automations aren't failing. That's the problem.
When a workflow crashes, you find out. When it runs, reports success, and quietly does nothing — you find out three days later, from your client.
Read-only API access
Runs outside your instance
Alerts to Slack or email
invoice-syncevery 15m
Completed
lead-routerevery 5m
Completed
crm-enrichevery 30m
Completed
nightly-exportdaily 02:00
Completed
lead-router stopped checking in 41 minutes ago — and n8n still reports every run as completed.
What breaks quietly
Four failures your error workflow will never catch
None of these throw. Every one of them is invisible until someone downstream complains.
The credential that expired
no HTTP status at allThe token fails at the signing step, before the request ever leaves. Error handling built around status codes never sees a thing.
The node that hangs
still running · foreverIn queue mode both the workflow Timeout and EXECUTIONS_TIMEOUT are ignored. Open as issue #36343 — reported three times, still unfixed.
The run that returns nothing
success · 0 rowsThe upstream source changed shape. Everything downstream processed an empty set — correctly, and pointlessly.
Two things I sell
Find them once. Then watch for them.
The audit tells you what's already broken. The monitor makes sure you're the one who finds out next time.
The Audit
One week · fixed scope
$500one-time
- Every workflow mapped, with what depends on what
- Which ones fail silently today, and exactly how
- Credential expiry exposure, per connection
- Cost per run, and which workflows burn money for no output
- What breaks first, ranked, with what it costs when it does
You keep the document whether or not you do anything else with me. It names specific workflows, and it's written so you can hand it to someone else.
Buy the audit
Recurring
The Monitor
External · read-only
$99per instance / month
- Heartbeat per workflow — alerts when a scheduled job stops checking in
- Output assertions — alerts on zero rows, or a count far off its normal
- Credential expiry warnings before the token dies, not after
- Alerts to Slack or email
It lives outside your n8n, so it still works when your n8n doesn't. It never writes to your instance.
Book a 20-minute call
For agencies
One instance is a nuisance. Twenty is your reputation.
You have this problem multiplied by every account you manage — and your clients find out before you do.
The monitor is available white-label: your name on the alerts, your dashboard, your margin. Bill it as part of your managed service. One conversation covers every client you have.
20 client instances · 4 currently silent · 0 alerts raised
Who you're dealing with
One person, and you get that person
I build and run automated systems that have to work unattended — scheduled agents, API pipelines, and a video production pipeline that renders and publishes on its own.
I built the monitoring because my own scheduled jobs were finishing with empty output and nothing was telling me. I fixed it for myself first.
There's no team, no account manager, and no sales process. You get me, and I answer my own email.
Straight answers
Before you ask
Why not just use n8n's error workflow?
It only fires on errors, and every failure above is a non-error. And if the instance is down or a worker is OOM-killed, there's nothing left running to send you anything.
Can't I build this myself?
Yes — several people on the n8n forum have, independently. That's how I know the problem is real. It's a weekend to build and forever to maintain, and it isn't your product.
Do you need access to my data?
No. Read-only API access. The monitor looks at execution metadata and result counts, never the contents.
What if the audit finds nothing?
You've paid $500 to learn your automations are sound, in writing. For a system doing work you depend on, that's a reasonable outcome.
Start here
Find out what's already broken
One week, $500, a written report you keep either way.