The Workflow Router step now supports returning the name of a step instead of the step object itself, and can route to a group of steps as a single choice.
This makes routing logic easier to define, reason about, and maintain—especially in larger workflows with shared paths or reusable subflows. Named and grouped routing reduces tight coupling between steps and lowers the operational cost of evolving workflows over time.
Why this matters:
- Cleaner, more maintainable routing logic
- Easier reuse of shared workflow paths
- Reduced refactoring risk as workflows grow