Playwright workflow use cases

Each page here builds one complete workflow on the canvas, from trigger to outcome. They all assume you have Playrunner running and a repository connected — if not, start with Get started with Playrunner.

They also share one idea worth understanding first: connection state. What happens after a Playwright run is decided by the kind of edge you draw out of it — on failure, on success, sequential, concurrent, or independent — rather than by a condition inside a script.

Reacting to results

• Slack alerts for failed Playwright tests — route failures to the right channel, with the run and report attached.
• Create Jira bugs from failed Playwright tests — open a ticket automatically, with run context in the fields.
• AI triage for Playwright test failures — summarise what broke before a human reads it.

Starting runs

• Scheduled Playwright test runs — nightly and recurring runs without a cron job in CI.
• Trigger Playwright tests from a webhook — run a suite when another system says so, and report back when it finishes.

Related

• Integration reference — every available node.