All templates
For ops teams, automation engineers & no-code builders

Hand off broken n8n workflows to the right person

Every hour, WebRun opens n8n, checks the execution history for workflows that failed since the last check, opens a Trello card naming the workflow, the node that failed, and the error message, and posts the card link to Microsoft Teams so a teammate can claim and fix it.

  • No credit card
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every hour WebRun
1 n8n check workflow execution history
2 Trello open a card for each failure
3 Microsoft Teams notify the on-call teammate
Run a sample
In short

How do I make sure a failed n8n workflow gets picked up by someone?

WebRun checks your n8n execution history every hour for failed workflow runs. For each new failure, it opens a Trello card naming the workflow, the node, and the error, then posts the card to Microsoft Teams so the on-call teammate can claim it, turning a silent failure into a tracked, assigned fix within the hour.

  • Every failed workflow gets a tracked card, not a missed alert
  • The on-call teammate is notified within the hour
  • No duplicate cards piling up for the same ongoing failure

Built for ops teams · automation engineers · no-code builders · internal tools teams

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 app.n8n.cloud/login in a real browser with your saved login - no setup, no API keys.

  2. 1
    n8n - check workflow execution history
    n8n.io
    WebRun in n8n: check workflow execution history
    WebRun opens n8n to check workflow execution history.
    • Open n8n and review the executions list for active workflows
    • Filter to runs that ended with an error since the last check
    • Capture the workflow name, the failing node, and the error message

    Done when Every workflow that failed since the last check is listed with its error.

  3. 2
    Trello - open a card for each failure
    trello.com How to Automate Trello
    WebRun in Trello: open a card for each failure
    WebRun opens Trello to open a card for each failure.
    • Open the automations board in Trello
    • Create a card per failed workflow with the error message and a link back to the n8n execution
    • Skip creating a duplicate card if one is already open for that workflow

    Done when Every new failure has exactly one open Trello card.

  4. 3
    Microsoft Teams - notify the on-call teammate
    microsoft.com How to Automate Microsoft Teams
    WebRun in Microsoft Teams: notify the on-call teammate
    WebRun opens Microsoft Teams to notify the on-call teammate.
    • Post the new Trello card link to the on-call channel in Microsoft Teams
    • Name the workflow and the failing node in the message
    • Leave the fix itself to whoever picks up the card

    Done when The on-call channel has a message for every new failure card.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.n8n.cloud/login
ScheduleRuns automatically on this cadence
Every hour
DeliveryHow each run's result reaches you
Failure card · Microsoft Teams
OutputWhat each run produces - One Trello card per failed n8n workflow, with the error message, plus a Teams notification pointing the on-call teammate to it.
List
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

Does it try to fix the workflow itself?

No. WebRun only reads the execution history and files a card with what broke. Editing or redeploying the workflow stays with whoever picks up the card.

Will I get a duplicate card for the same ongoing failure?

No. It checks for an already-open card on that workflow before creating a new one, so a repeated failure does not spam the board.

How fast does the team find out about a failure?

Within the hour. Each check posts straight to Microsoft Teams, so a broken workflow does not sit undiscovered until someone happens to open n8n.

Put this on autopilot.

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