Workflow Alerts That Only Fire When They Should
Instead of notifying you on every run, a workflow now defines rules that describe why it should interrupt you, and a run that matches nothing stays completely silent.
Screenshots
These screenshots come from the same app-side Latest Features gallery used in the product experience.
Current release version for Workflow Alerts That Only Fire When They Should: 0.261.001
Conditions cover run status, task status, output text that contains, does not contain, or matches a regular expression, File Sync results, empty output, a signal raised by an agent, and a plain-English condition judged by a model such as “any certificate expires within 14 days”. Each rule can watch the final output, any task output, or one specific task. Severity runs info, low, medium, high, and critical: info and low land quietly in the notification bell while medium and above open the pop-up. When several rules match, the highest severity wins and the alert lists every matched rule under Triggered by.
Why It Matters
This matters because a workflow that notifies you on every single run gets ignored, which defeats the point of running it unattended.
How to Try It
- Open Personal Workspace and go to the Workflows section.
- Open a workflow and step through the builder to Review.
- Switch the alert mode from the simple setting to rules.
- Add a rule and choose a condition, such as output text matching a phrase you care about.
- Set the severity, remembering that info and low stay in the notification bell.
- Save, then run the workflow and confirm a non-matching run stays silent.
- Trigger a matching run and check the Triggered by section on the alert.
Where to Find It
- Open Personal Workspace — Add conditional alert rules in the workflow builder Review step.