Create Automation

The posture of this trigger, either Reactive or Proactive. Reactive triggers respond to the presence of the expected events, while Proactive triggers respond to the absence of those expected events.

The event(s) which must first been seen to fire this trigger. If empty, then fire this trigger immediately. Events may include trailing wildcards, like prefect.flow-run.*

The event(s) this trigger is expecting to see. If empty, this trigger will match any event. Events may include trailing wildcards, like prefect.flow-run.*

Evaluate the trigger separately for each distinct value of these labels on the resource. By default, labels refer to the primary resource of the triggering event. You may also refer to labels from related resources by specifying related:<role>:<label>. This will use the value of that label for the first related resource in that role. For example, "for_each": ["related:flow:prefect.resource.id"] would evaluate the trigger for each flow.

The unique ID of this trigger

Labels for resources which this trigger will match.

Labels for related resources which this trigger will match.

The number of events required for this trigger to fire (for Reactive triggers), or the number of events expected (for Proactive triggers)

The time period over which the events must occur. For Reactive triggers, this may be as low as 0 seconds, but must be at least 10 seconds for Proactive triggers

The posture of this trigger, either Reactive or Proactive. Reactive triggers respond to the presence of the expected events, while Proactive triggers respond to the absence of those expected events.

The event(s) which must first been seen to fire this trigger. If empty, then fire this trigger immediately. Events may include trailing wildcards, like prefect.flow-run.*

The event(s) this trigger is expecting to see. If empty, this trigger will match any event. Events may include trailing wildcards, like prefect.flow-run.*

Evaluate the trigger separately for each distinct value of these labels on the resource. By default, labels refer to the primary resource of the triggering event. You may also refer to labels from related resources by specifying related:<role>:<label>. This will use the value of that label for the first related resource in that role. For example, "for_each": ["related:flow:prefect.resource.id"] would evaluate the trigger for each flow.

The unique ID of this trigger

Labels for resources which this trigger will match.

Labels for related resources which this trigger will match.

The number of events required for this trigger to fire (for Reactive triggers), or the number of events expected (for Proactive triggers)

The time period over which the events must occur. For Reactive triggers, this may be as low as 0 seconds, but must be at least 10 seconds for Proactive triggers