Automated Power Apps Connection Monitoring
Every morning, WebRun opens the Power Apps maker portal, checks every connection for an expired or broken sign-in, reads the overnight run history of your flows for failures, opens a Trello card for each problem with the app or flow name, and sends the maker team a WhatsApp summary of what is broken.
How do I find broken Power Apps connections and failed flows each morning?
WebRun opens the Power Apps maker portal every morning, checks every connection for an expired or broken sign-in, and reads the overnight run history of your flows for failures. It opens one Trello card per problem with the error text and dependent apps, then sends the maker team a WhatsApp summary.
- Broken connections are found before a user reports them
- Every failure has a card with the actual error text
- Repeat failures collapse into one card with a run count
Built for Power Platform admins · citizen developers · IT teams · operations managers
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
make.powerapps.comin a real browser with your saved login - no setup, no API keys. -
1
Microsoft Power Apps - check connections and run history
powerapps.microsoft.com
WebRun opens Microsoft Power Apps to check connections and run history. - Open the Power Apps maker portal and go to your connections list
- Capture every connection showing an error or asking to be signed in again
- Open the run history for your flows and capture overnight failures with the error shown
- Note which apps depend on each broken connection
- Read only. Never republish an app, edit a flow, or re-enter a credential
Done when Every broken connection and failed run from overnight is captured with its owner.
-
2
Trello - raise a card per failure
trello.com
WebRun opens Trello to raise a card per failure. - Open your maker board and add a card for each broken connection or failing flow
- Title it with the app or flow name and paste the error text into the description
- List the dependent apps so the blast radius is obvious
- Label anything customer-facing as urgent
- Skip items that already have an open card
Done when Every failure has exactly one open Trello card with its error text.
-
3
WhatsApp - brief the maker team
whatsapp.com
WebRun opens WhatsApp to brief the maker team. - Send the maker team a short WhatsApp summary of this morning's failures
- Lead with connections needing a sign-in, since those block everything downstream
- Give the count of failed runs overnight and name the worst offender
- Say plainly when everything ran clean
Done when The maker team knows what is broken before the first user calls.
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 republish anything?
No. WebRun reads the maker portal only. It never republishes an app, edits a flow, re-enters a credential, or re-runs a failed job. A maker makes every change by hand.
Does it handle credentials?
No. It reports that a connection needs signing in again and names which one. It never types, stores, or re-enters a password or an API key on your behalf.
Will one flaky flow flood the board?
No. It groups repeated failures of the same flow into a single card with a run count, and skips anything that already has an open card until you close it.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.