Skip to main content
A trigger runs a set of flows when your application deploys, or on a schedule. Triggers belong to the workspace, so one trigger can cover staging, production and every preview environment. You create and edit triggers on the workspace’s triggers page, or through the public API and CLI.

Trigger kinds

  • Deployment — fires when your pipeline notifies QA Wolf of a successful deploy that matches the trigger’s conditions. The flows run against that deploy. See PR testing and the deployment testing guides for how the notification reaches QA Wolf.
  • Schedule — fires in one environment every few hours, days, weeks or months. An hourly or daily schedule can be restricted to chosen days of the week. Needs nothing from your pipeline.

What a trigger runs

  • A tag — every flow carrying it. Flows tagged later join automatically.
  • Named flows — a fixed set.
  • A Smart Smoke Suite, labeled Let QA Wolf choose from the pull request’s changes on the triggers page — flows QA Wolf selects from the pull request behind the deploy. Deployment triggers only, and only for deploys tied to a pull request. See PR testing.
Give preview deploys their own trigger rather than widening the one that covers staging. A pull request rarely needs everything staging runs, and a Smart Smoke Suite skips every deploy that has no pull request.

Mobile apps

A mobile pipeline uploads each new build and reports it as a deployment. The runs a deployment trigger starts install that build. A scheduled run installs the environment’s latest build. When Android and iOS both report into one environment, give each platform its own trigger with a service condition. See Mobile build testing.

Create a trigger

On the triggers page, select Create trigger. The drawer asks what should start the runs:
  • Deploys to an environment — a deployment trigger for staging, production or any long-lived environment.
  • A schedule — runs in one environment on a repeating schedule. Pick a shortcut such as Hourly, Weekdays or Every 2 weeks, or set Every [N] [unit] at [time].
  • Pull request previews — a deployment trigger for preview environments named like a pattern, such as pr-*. It can let QA Wolf choose the flows from each pull request’s changes, or always run the same flows.
A sentence at the top of the drawer describes what the trigger does and updates as you edit. For a deployment trigger, it also says how many of your recent deploys the trigger would have run on, and lists them. To narrow a deployment trigger, select Only when… and add a repository, service, branch or deploy URL condition. Each condition suggests the values your recent deploys reported, and you can type a name or pattern instead. To choose what runs, select Add tags or flows. One search finds both, and a trigger can combine tags with flows named one by one. Run options holds failure investigation and the number of flows that run in parallel.

Pausing

A paused trigger never fires. Resuming brings back the same configuration. A resumed schedule picks up at its next slot, and slots it missed while paused don’t run.

Reference

  • Trigger fields — conditions, schedule and action fields.
  • Deployments — how QA Wolf reads a deployment, and the verdict it records for each trigger.
Older workspaces may still run legacy triggers, which attach to a single environment. See Migrate from legacy triggers to move them.
Last modified on November 9, 2026