n8n Silent Success Guard: REST API Monitor & Alerts
n8n Silent Success Guard: REST API Monitor & Alerts
Regular price
£14.99
Regular price
£14.99
Sale price
Unit price
/
per
⬇
Instant Digital Download
∞
Unlimited Downloads
★
Lifetime Access in Your Account
Couldn't load pickup availability
🔥
128+ Sold
Popular with n8n builders
⚡
23 people viewing
High interest right now
✅
9 added today
Fast-moving digital product
n8n Silent Success Guard: REST API Monitor & Alerts
Regular price
£14.99
Regular price
£14.99
Sale price
Unit price
/
per
Catch “successful but empty” runs in n8n—automatically monitor and alert before silent failures
The n8n Silent Success Guard: REST API Monitor & Alerts workflow checks your n8n instance every six hours, finds successful executions that produced zero output items, and sends you a clear list of those “green but empty” runs to your chosen alert destination. It helps you detect silent misconfigurations where a workflow ends in success yet produces nothing.
What this workflow does
- Scheduled monitoring: Runs every six hours on a schedule trigger.
- Fetch successful executions via REST API: Calls your n8n REST API to retrieve up to 100 executions with status set to success, including execution data.
- Detect “silently empty” runs: Reviews each execution’s run data to identify cases where the last executed node produced zero output items.
- Smart skipping: Skips executions that have no attached run data, are very short, or end with nodes expected to output nothing (for example NoOp or Stop and Error).
- Alert-ready output: Produces a list containing workflow name/ID, execution ID, start time, and last node executed so you can route flagged results to your monitoring channel.
Use cases
- Ensure SaaS automations don’t “succeed” without generating downstream data (e.g., reports, updates, or records).
- Catch edge cases after workflow changes where the final node completes but outputs nothing.
- Provide operators and automation engineers with actionable alerts instead of silent green runs.
Technical details
-
Environment variables: Set
N8N_BASE_URLandN8N_API_KEY(API key must allow reading executions). - Integration: n8n REST API execution querying (success status, execution data included).
- Nodes used: Schedule Trigger, HTTP Request, Code, No Op, Sticky Note.
- Retention requirement: Ensure execution data retention/pruning lasts longer than the six-hour interval (or reduce the schedule).
- Destination step: Replace the placeholder final step with your alert destination (e.g., Slack, email, or a database).
