Description
Workflows now includes a guided Basic mode to build trigger filters from the trigger schema using conditions and AND / OR logic, without writing JSONPath. Advanced JSONPath remains available. This continues the work we started with easier trigger filter testing: missing-filter warnings and a test experience that shows whether your filter matches. Together, these updates make it easier to add a meaningful filter so you can reduce unintended workflow executions that drive high execution counts and reach workflow limits.
Action required: Staging and Production gap
Read this before you promote any workflow during rollout.
Staging and Production will not get this update on the same day. Production trails Staging because of Navigate.
| Environment | Trigger filter format during the gap |
|---|---|
| Staging | New format (this update) |
| Production | Older format (until Production is enabled) |
If you upload a workflow JSON that uses the other environment’s trigger filter format, the upload will fail. Remove the trigger filter from the definition first, then upload the file and add the filter again in the UI of the target environment.
This applies to JSON and API updates. You can still edit workflows in Production through the UI.
Safer option if you prefer not to adjust: Keep building in Staging, and wait to promote until Production has this update.
What You Need to Know
-
Rollout gap first: Staging enables before Production. If you upload a workflow JSON that uses the other environment’s trigger filter format, the upload will fail. Remove the trigger filter from the definition first, then upload the file and add the filter again in the UI of the target environment.
-
Already available: As part of this work, Workflows already warns when a filterable trigger has no filter, and testing applies your trigger filter against the test input so you can see whether the filter matches. See Easier Trigger Filter Testing in Workflows.
-
Basic and Advanced: Build filters in Basic mode from the trigger schema, or continue in Advanced with JSONPath. Both store one trigger filter.
-
Optional today: Filters remain optional, but they are highly recommended.
-
Basic mode: Conditions come from the trigger schema. Array fields are not available in Basic in this release.
-
Advanced mode: JSONPath on arrays still works, including
$.changes[?(@.attribute == "department")]. -
Existing workflows: Enabled workflows keep running as they do today. With this update, View, Edit, Download, and List present trigger filters in the new format.
Problem
Writing JSONPath filters is challenging, and not everyone is an expert. Without an easier way to author filters, they get skipped or left too broad, which can lead to unintended executions, high execution counts, and workflow limits being reached.
Solution
This update adds the guided builder on top of the earlier trigger filter improvements.
- Basic mode (new): Guided condition builder from the trigger schema (AND / OR)
- Advanced mode: Continue authoring with JSONPath when you need full expression control
- Already available: Missing-filter warnings, plus test feedback that shows whether the filter matches your test input
Who is affected?
Org Admins who edit Identity Security Cloud Workflows.
Action required: During the Staging to Production gap, if you upload a workflow JSON that uses the other environment’s trigger filter format, the upload will fail. Remove the trigger filter from the definition first, then upload the file and add the filter again in the UI of the target environment.
Action highly recommended: Try the new Basic filter builder on a filterable event trigger, use the improved test experience to confirm the filter matches your test input, and share your feedback in this thread.
We want your feedback
Please try the new trigger filter builder experience in Staging and tell us how it goes. Reply in this thread with what worked well, what was confusing, and any gaps you hit.
Important dates
Staging: September 14, 2026 · September 16, 2026
Production: Mid-October
During the window between Staging enablement and Production: Staging and Production use different trigger filter formats. If you upload a workflow JSON that uses the other environment’s format, the upload will fail. Remove the trigger filter from the definition first, then upload the file and add the filter again in the UI of the target environment.
Where to learn more
- Earlier in this work: Easier Trigger Filter Testing in Workflows
- Building and testing workflows: Testing a Workflow