The run is green and the CRM is empty
A filter, a bad mapping, or a webhook that returns nothing still counts as success in n8n. The Error Trigger never fires.
For agencies running client automations
A workflow can stay green while the CRM stays empty. LeadPulse watches silence, zero-item runs, and dead triggers, then tells you once.
No card for the trial.
Workflow status
Meta lead ads to CRM
n8n · Marlow & Birch
Website form intake
Silent 11 hours
Invoice sync
Make heartbeat · 40m late
Review requests
31 records this week
What gets missed
A filter, a bad mapping, or a webhook that returns nothing still counts as success in n8n. The Error Trigger never fires.
Someone unpublished the workflow, the schedule drifted, or the source app stopped calling. There is no error because there is no run.
Yesterday this scenario wrote 40 leads. Today it has written two, and nobody is going to notice until the client asks.
How it works
01
Paste the n8n base URL and an API key. LeadPulse imports workflows and reads executions. Make, Zapier, and custom agents use a heartbeat URL instead.
02
Silence after N hours. Zero-item successes, allowed or not. Deactivation. Error rate. A drop against the trailing 7-day pace.
03
Email, Slack, or Telegram. The checker runs every 10 minutes and will not spam you. When the workflow starts delivering again, you get a recovery note.
04
Agency plans get a white-label health report per client: uptime, runs, records, and incidents. Share the link or let us email it.
Sample report
A white-label week for a fictional studio. Uptime, runs, failures, records, incidents with time to detect, and a plain-English summary. The page below is the same component a real share link uses.
Example · fictional client data, not a live account
Fieldnote Studio
Automation Health Report
Last week
19 Oct 2026 – 26 Oct 2026
The website form for Marlow & Birch stopped delivering on Tuesday afternoon. LeadPulse opened an incident 11 minutes after the silence rule tripped, before anyone at Fieldnote Studio had checked the CRM. Meta lead ads stayed healthy and wrote 186 records. Invoice sync in Make missed its heartbeat for 40 minutes and recovered the same morning.
| Workflow | Uptime | Runs | Failures | Records |
|---|---|---|---|---|
| Meta lead ads to CRM | 100% | 42 | 0 | 186 |
| Website form intake | 86.4% | 6 | 1 | 14 |
| Invoice sync | 97.1% | 18 | 0 | 9 |
| Review request sequence | 100% | 31 | 0 | 31 |
Website form intake has been silent for 11 hours
The workflow stayed active. The last successful run wrote 14 records. Nothing finished after 14:02 UTC on Tuesday.
Since 20 Oct, 14:02 UTC · recovered 21 Oct, 09:18 UTC · time to detect 11 minutes
Invoice sync heartbeat was late
The Make scenario missed its 30-minute heartbeat. The next ping arrived with 1 record and the incident closed.
Since 22 Oct, 08:10 UTC · recovered 22 Oct, 08:50 UTC · time to detect 9 minutes
An example incident alert, with the same message text the product sends, sits on the sample report.
Pricing
The 14-day trial does not ask for a card. Agency adds clients and the white-label Monday report. Pro removes the caps.
Solo
$29/mo
One n8n instance for a builder running their own lead flow.
Most agencies
$79/mo
Up to 10 clients, with a white-label Monday health report.
Pro
$149/mo
Unlimited instances, workflows, heartbeats, and clients.
The Error Trigger only sees failed executions. It misses a deactivated workflow, a trigger that stopped firing, and a success that processed zero leads. Those are the outages agencies actually get blamed for.
After you sign up and connect an instance, the key is encrypted at rest. The free audit uses the key for that one request and does not save it.
Add a heartbeat step at the end of the scenario. It calls a unique URL, optionally with ?count=. If the call is late, or the count is 0, LeadPulse alerts.
The trial does not ask for a card. When it ends, checks stop and the dashboard becomes read-only until you subscribe. Solo is $29, Agency is $79, Pro is $149.
Yes. Each weekly report has an unguessable link. On Agency and Pro the page uses your logo and name, not ours. A fictional example is on the sample report page.