For the complete documentation index, see llms.txt. This page is also available as Markdown.

Automations

Trigger work automatically on a cron schedule, or when a run finishes — run a feature suite, a load test, or an AI assistant job.

Automations run work without a manual start. Each automation pairs a trigger — a time-based cron schedule, or when a run finishes — with an action: run a feature suite, run a load test, or run an AI assistant job.

The Automations view

Create An Automation

  1. Select Automations from the navigation rail.

  2. Select + (New automation) in the list rail.

  3. Name it, then choose a Trigger mode:

    • Time (cron) — pick a schedule preset and timezone (for example, daily at 02:00 UTC).

    • When a run finishes — run automatically after a run completes; optionally only when it finished passed or failed.

  4. Choose an Action:

    • Run features (a suite) — set the site URL, the features to include, and a configuration.

    • Run a load test — pick a load-test feature and an optional site URL.

    • Run AI assistant — give the assistant a prompt to run headlessly, with an optional site URL and email for the report.

  5. Make sure Enabled is on, then Save.

Each firing produces exactly one run, even when a Run features action covers many features — they dispatch together as a single suite run rather than one run per feature, so history stays readable and the automation's "last run" always points at one result.

Manage Automations

Control
What it does

Enabled toggle

Pauses or resumes the automation without deleting it. Disabled automations keep their configuration.

Run now

Dispatches the automation immediately — useful to verify settings before trusting the schedule.

Last run indicator

Each list entry shows when the automation last dispatched.

An automation-produced run notifies the same way a manually started run does — see Notifications to configure email, Slack, Google Chat, or Microsoft Teams delivery.

Good Defaults

  • A nightly full-suite regression at a quiet hour catches drift without slowing anyone down.

  • A regression suite that runs when a smoke run passes chains coverage without manual hand-off.

  • Point scheduled automations at a stable environment — a staging URL that resets overnight will fail for reasons unrelated to your app.

Last updated

Was this helpful?