For teams whose Playwright suite already runs in Certyn once, and who want it every night without a CI job.

Your setup

Playwright tests in a GitHub repo, with GH_TOKEN saved (see the first recipe).
A staging environment on the internet.
You want a run every night at a fixed time, in your time zone.

Say this to Certyn

Run our Playwright suite against staging every night at 2am Berlin time.

Checks that it has repo access and the saved repo and test command. If the suite has not run in Certyn yet, run it once from the chat first.
Creates an agent process (app.process.create type agent) with the same goal: clone the repo, install, run npx playwright test against the environment, report. It asks you to confirm.
Sets the schedule for staging (app.process.trigger.set): cron 0 2 * * *, time zone Europe/Berlin. You approve the settings change.
Each night the process starts a run by itself.

A run report each morning, with failures grouped by cause.
New issues only for new product bugs. Known bugs are not filed again. Fixed bugs are retested.
The history of every night's run on the process.
If you want, a morning email that answers your own question, for example what failed last night? (app.morningemail.set).

A scheduled run has 60 minutes. For a longer suite, split it into two processes, for example by Playwright project or folder, each with its own goal.
GitHub App rules (pull request, merge, push) run only Certyn test-case suites, not a goal like this. For a run after each deploy, turn on "after each deploy" for the same process; a deploy is a new environment version.
Each night uses plan time for as long as the run takes.