Skip to main content
Every trigger has a name, a paused state, one occasion (deployment conditions or a schedule) and one action.

Deployment conditions

Every condition supplied must match. A trigger with no conditions fires on every deployment the workspace receives. The environment name a deployment carries decides whether the trigger sees it. See Deployments.

Schedule

A created schedule reports nextScheduledAt.

Action

An action names at least one flow or tag, or is a generativeSuite. A generativeSuite action:
  • Refuses flowIds and tagNames.
  • Is only valid on a deployment trigger.
  • Skips any deploy that is not tied to a pull request, with the verdict reason no-pull-request. See PR testing for what ties a deploy to its pull request.

Paused

A paused trigger is never evaluated. Pausing and resuming change nothing else on the trigger.
Last modified on September 22, 2026