Leads go nowhere for days
A broken lead capture workflow means prospects wait without an answer. Some move on.
Your workflow ran. Nothing arrived.
Point Nilwatch at where your output should land. If nothing new shows up on schedule, you get an alert — before your users notice.
Start free →
Free to join · No credit card
Works with no-code tools like
- n8n
- Zapier
- Make
- Google Sheets
- Slack
- AI agents
- Webhooks
The risk
It only takes one silent failure.
No-code tools let anyone automate complex workflows. That's amazing. But they can break quietly. When they do, you're the last to know.
Your data falls behind, silently
A broken sync means stale records, duplicate work, and decisions made on bad data.
SLAs get missed
If you promised a client timely data processing, a silent failure can cost you the relationship.
You find out from a user
The worst way to learn about a broken workflow is a support email. Nilwatch tells you first.
And the workflow log says "success" the whole time.
How silent failures hide
What you don't see
This is how it goes wrong. The workflow ran. It reported success. Nothing arrived.
2:00 AM — Your workflow runs and reports succeeded.
The automation fires on schedule. The status log shows green. Everything looks fine.
8:00 AM — Nothing has landed in the Sheet.
The row count hasn't moved. Leads are piling up — or disappearing into nothing.
3 days later — A client asks why nothing was processed.
You trace it back. A column rename broke the mapping. The workflow never errored. 72 hours of data is gone.
With Nilwatch — Alert at 8:04 AM.
Nilwatch noticed nothing landed. You get an email before anyone complains.
How it works
Catch it in minutes, not days
No code needed. If you can fill in a form, you can set up Nilwatch.
01
Connect your destination
Point Nilwatch at a Google Sheet, a JSON endpoint, or a webhook — wherever your workflow drops its output.
02
Set a schedule
Tell Nilwatch how often new output should arrive: every hour, every day, or another window.
03
Get alerted
If nothing new shows up in time, you get an email or Slack message — even when your workflow says it succeeded.
Who it's for
Solo founders and small agencies running lead capture, email sequences, or data sync workflows in n8n, Zapier, Make, or AI agent pipelines. If you rely on a workflow and would not know for days if it broke, Nilwatch is for you.
Features
What Nilwatch monitors
Destinations, alert channels, and the no-code tools Nilwatch works with.
Destinations we watch
- Google Sheets — Watch for new rows on a public or shared sheet.
- Inbound webhook — Your workflow POSTs its output count. An empty count is a failure.
- HTTP JSON — A public URL and a count path, such as a list length or a total.
Alert channels
- Email — Sent the moment a check fails.
- Slack — Route alerts straight to your Slack channel.
Works with
- n8n — Any workflow that writes to a destination.
- Zapier — The Sheet or webhook your Zap writes to.
- Make — Scenarios that run but don't write.
- AI agent pipelines — Watch the output from any agent workflow.
What an alert looks like
You hear about it right away
When nothing shows up, Nilwatch sends a clear message. Here is what one looks like.
Nilwatch: Lead import produced nothing
What happened: Your Zapier zap ran and reported success, but the row count in your Google Sheet hasn't changed in 6 hours. Nilwatch noticed and sent this alert.
Email · Slack
Lead import is quiet. Increased by 0 over 6 hours. Expected at least 1. Open the monitor: https://nilwatch.app/monitors/4821
Fixed in 20 minutes
"A column rename broke the mapping. Fixed and re-ran. 847 leads imported."
Resolved
Example for illustration only. Not a real customer.
Example
From missed leads to caught in time
An example of a workflow failure caught early versus one that ran undetected for days.
lead-import · Google Sheet
Silent failure · 3 days unnoticed
- Lead import silent for 3 days
- 847 leads never processed
- Found out from a client
alert in 4 h
lead-import · Google Sheet
Caught in time · Alert fired in 4 h
- Alerted 4 hours after failure
- Fixed before clients noticed
- Zero missed leads
Example for illustration only. Not a real customer.
The cost
Your options, side by side
You could check every workflow by hand. You could chase it down when someone complains. Or you could set up Nilwatch.
Hire a developer
$500+ — often, for one integration
- Days or weeks to book
- Needs access to your tools
Check it manually
30 min+ — every day, per workflow
- Easy to forget or skip
- Catches it only after the fact
Nilwatch — No-brainer
4 minutes — to set up, then automatic
- Plain alert, no jargon
- Catches it inside the window you set
Typical estimates to compare options. Not quotes. Real costs vary.
Is it safe?
What do you actually do?
Here is exactly what Nilwatch reads, and what it doesn't.
- We count output, not sheet cells
- On a sheet, Nilwatch checks whether new rows arrived. It does not store the cells. A JSON check reads only the count path. A webhook stores the payload the workflow posted, trimmed.
- No workflow credentials
- We connect to your output destination, not your workflow tool. No keys for n8n, Zapier, or Make.
- Read-only access
- We only read. We never write, delete, or modify anything.
- We don't store your rows
- Row counts and timestamps only for sheets. We never store the actual content of your rows.
- Your monitors are private
- Only you can see your monitors and their history. Nothing is public.
- Automated checks only
- Checks run on your schedule. No person looks at your data.
Pricing
Free to start. Solo is $19 a month.
Set up your first monitor for free. Pay only when you need more.
Free
$0/mo
- 2 monitors
- Email and Slack
- Any window we offer
- Alert history
Solo
$19/mo
- 20 monitors
- Email and Slack
- Any window we offer
- Alert history
Team
$49/mo
- 100 monitors
- You plus 8 teammates
- Email and Slack
- Alert history
Monthly subscription. Cancel in the Stripe customer portal. Safe checkout with Stripe.
FAQ
Questions, answered
Does it work if my workflow says it succeeded?
Yes. That is exactly what Nilwatch is for. We do not connect to your workflow tool at all — we watch the output destination directly. The workflow log has nothing to do with our check.
What output destinations do you support?
A public Google Sheet or CSV, an HTTP JSON count, and an inbound webhook your workflow calls. More integrations can be added.
What counts as "nothing new showing up"?
You choose the window: every hour, every day, or another window we offer. If no new output arrives within that window, Nilwatch fires an alert. An empty webhook count fails as soon as it arrives.
Do I need to change my workflow?
Not for a sheet or a JSON count. Point Nilwatch at where the output lands. A webhook monitor needs one HTTP step that posts the output count. No keys for n8n, Zapier, or Make.
Is it a subscription?
Yes. Free includes 2 monitors. Solo is $19 a month for 20 monitors. Team is $49 a month for 100 monitors and extra alert recipients. Cancel in the Stripe customer portal.
What alert channels do you support?
Email and Slack. Every alert is also stored in your Nilwatch inbox, including when email is not configured yet.
Will it alert for empty rows?
Yes. Zero new rows within your window triggers the alert, regardless of whether the workflow itself reports success.
Who is this for?
Solo founders and small agencies running lead capture, email sequences, or data sync workflows in n8n, Zapier, Make, or AI agent pipelines. If you rely on a workflow and would not know for days if it broke, Nilwatch is for you.
Ready?
Watch your first workflow before it breaks
Free. Quick to set up. No code.