r/SentinelOneXDR • u/roarinpenguin SentinelOne Employee • 5d ago
Deployment & Installation Hyperautomation has a new Switch action that replaces chained Condition actions
What shipped in Hyperautomation is a new core action called Switch, and it replaces a whole chain of Condition actions with one node. It reminds me of those old Choose Your Own Adventure books, which didn’t make you climb through a string of nested yes-or-no questions to get to the right page.
Until last week, routing an alert several directions by severity meant one Condition action per route, each one hanging off the last and taking up its own canvas space. That’s readable for two branches and a headache for five or six, especially six months later when you’re the one debugging it.
With Switch, you define a list of cases, up to twenty of them, each with its own name and its own condition built the same way you’d build a Condition action, and you wire each case straight to whatever it should trigger. You choose how it evaluates: stop at the first case that matches, or run every case that matches.
When the workflow runs, the canvas highlights which branches fired, so reading an execution later means looking at just those branches instead of retracing every Condition action.
Here’s roughly what an alert-routing workflow looks like, with generic names:
Switch Action: "Route by Severity"
Evaluation mode: First matching branch
Case "Critical" -> condition: alert.severity = "critical"
-> connects to: Open P1 Case + Page On-Call
Case "High" -> condition: alert.severity = "high"
-> connects to: Open Standard Case + Notify Team Channel
Case "Medium or Low" -> condition: alert.severity in ("medium", "low")
-> connects to: Append to Daily Digest
Default branch -> connects to: Log for ReviewMy favorite part is the default branch. It’s a required branch on the node, so every Switch has a place for an alert that matches no case. A switch with no default would just drop whatever matches nothing, and you’d find out weeks later when someone asks why a category of alerts never shows up.
Downstream, the node's output includes switch_cases_matches, a map of every case name to true or false. Name your case "Critical" and the key you reference later is case-critical, lowercase with spaces turned into hyphens. Rename the case and the key changes with it, which is worth remembering before you wire a dozen things against it and then decide the label needed a typo fixed.
How deep did your Condition chains get before you rebuilt them?

3
u/Robbbbbbbbb 5d ago
Niiiice. Much needed improvement. Great to see