Automated n8n Workflow Health Reporting
Every Monday, WebRun opens n8n, reads the last seven days of executions for each active workflow, writes the run count, success rate, and average duration into Airtable, and saves a dated scorecard document to Google Drive with the workflows that got worse.
How do I track which n8n workflows are failing each week?
WebRun reviews your n8n execution history every Monday. It counts each active workflow's runs, successes, failures, and average duration over the past seven days, writes them into Airtable for a week-over-week comparison, and files a dated scorecard in Google Drive that leads with the workflows getting worse.
- Failing workflows surface weekly instead of when someone complains
- Every workflow has a dated reliability history in Airtable
- The scorecard names the workflows that got worse, ranked first
Built for automation engineers · ops teams · agencies · internal tools teams
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.n8n.cloud/loginin a real browser with your saved login - no setup, no API keys. -
1
n8n - read the week's executions
WebRun opens n8n to read the week's executions. - Open n8n and go to the Executions list
- Filter to the last 7 days across all active workflows
- For each workflow, count total runs, successes, and failures
- Note the average run duration and the last failure reason where one exists
Done when Every active workflow has a run count, a success rate, and a duration for the week.
-
2
Airtable - record run counts and success rates
WebRun opens Airtable to record run counts and success rates. - Open your Airtable workflow-health base
- Add this week's row for each workflow with runs, success rate, and average duration
- Compare against last week's row and mark the direction of travel
- Flag any workflow whose success rate dropped below your threshold
Done when Airtable holds one dated row per workflow with the week-over-week direction.
-
3
Google Drive - file the weekly scorecard
WebRun opens Google Drive to file the weekly scorecard. - Open Google Drive and create this week's scorecard document in your automation folder
- Lead with the workflows that got worse, then the ones that improved
- List every workflow that failed at least once with its last failure reason
- Name the file by week so the history stays browsable
Done when A dated scorecard for the week is saved in Drive.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it retry or edit my workflows?
No. WebRun only reads the execution history. It never re-runs a workflow, never activates or deactivates one, and never edits a node, so the scorecard is purely an observation of what already happened.
What counts as a failed run?
Any execution n8n itself marks as failed or stopped with an error. WebRun uses n8n's own status rather than guessing, and it copies across the last failure reason it shows.
Can I compare this week against previous weeks?
Yes. Every run appends a dated row per workflow in Airtable, so the base builds a full history and the scorecard shows the week-over-week direction for each workflow.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.