All templates
For Power Platform admins, citizen developers & IT teams

Catch broken app connections before users do

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.

  • 7-day free trial
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every day at 7:30 AM WebRun
1 Microsoft Power Apps check connections and run history
2 Trello raise a card per failure
3 WhatsApp brief the maker team
Run a sample
Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens make.powerapps.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Microsoft Power Apps - check connections and run history
    powerapps.microsoft.com
    WebRun in Microsoft Power Apps: check connections and run history
    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.

  3. 2
    Trello - raise a card per failure
    trello.com How to Automate Trello
    WebRun in Trello: raise a card per failure
    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.

  4. 3
    WhatsApp - brief the maker team
    whatsapp.com How to Automate WhatsApp
    WebRun in WhatsApp: brief the maker team
    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 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

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
make.powerapps.com
ScheduleRuns automatically on this cadence
Every day at 7:30 AM
DeliveryHow each run's result reaches you
Failure summary · WhatsApp
OutputWhat each run produces - A daily list of Power Apps connections needing re-authentication and overnight flow failures, each with a Trello card.
Text
Setup & safety

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.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

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.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.