Automated Activepieces Flow Health Digest
Every morning, WebRun opens Activepieces, reviews every flow's run history from the past day, tallies successes and failures, posts a health digest to Microsoft Teams, and books a fix session on Google Calendar for any flow that failed more than twice.
How do I monitor Activepieces flow failures across my workspace?
WebRun reviews every Activepieces flow's run history each morning, tallying successes and failures from the past day and posting the results as a health digest in Microsoft Teams. Any flow that failed more than twice gets a fix session booked on Google Calendar automatically, so a quietly broken automation gets caught before it costs real time.
- Broken flows surface the same morning, not weeks later
- Repeat failures get a fix session booked automatically
- Every flow gets checked, not just the ones on someone's mental list
Built for Operations teams · no-code automation builders · IT teams · small engineering 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
cloud.activepieces.comin a real browser with your saved login - no setup, no API keys. -
1
Activepieces - review yesterday's flow runs
activepieces.com
WebRun reviews yesterday's flow runs in Activepieces. - Open the run history for every active flow
- Tally successes and failures for the past day
- Note the error message for any failure
Done when Every flow's run counts for the day are captured.
-
2
Microsoft Teams - post the health digest
microsoft.com
WebRun posts the health digest in Microsoft Teams. - Post a digest of successes and failures per flow
- Include the error message for anything that failed
- Highlight flows with more than one failure
Done when The team has today's flow health digest in Teams.
-
3
Google Calendar - book a fix session for repeat failures
calendar.google.com
WebRun books a fix session on Google Calendar for repeat failures. - Book a fix session for any flow that failed more than twice
- Invite whoever owns that flow
- Attach the error details to the event
Done when A fix session exists for every repeatedly failing flow.
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 fix or restart a failing flow?
No. WebRun only reports and tracks failures. Fixing or restarting a flow stays a manual step for whoever owns it.
What counts as a repeat failure worth a fix session?
Any flow that failed more than twice in the past day. That pattern is usually a real problem, not one bad input.
Does it check every flow in the workspace?
Yes. Every active flow gets reviewed each morning, not just the ones people remember to check.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.