Workflow Automator - Ability to have multiple branches off of a Condition

You’re describing something very similar to switch/case logic (multiple branches off a single condition) instead of the current yes/no split. Right now, most workflow tools only let you evaluate one outcome at a time, which is why you end up duplicating the same condition field across multiple steps.

A couple of options you might consider:

1. Use a “Switch” or “Case” action – Some platforms (like Power Automate, Zapier, or advanced workflow builders) already support this, where you can branch once on a field value and send each option down its own path. If your tool doesn’t have it, it’s worth checking if there’s a feature request or beta.

2. Workarounds: You can sometimes simulate multi-branching by nesting conditions or using a single condition step with multiple outcomes mapped (e.g., “If dropdown = A → Team A, If dropdown = B → Team B”). It’s not always pretty, but it avoids repeating the same field check multiple times.

3. Rejoining flows: Some workflow platforms let you merge paths back together using connectors or shared subsequent steps. If not, you usually have to duplicate the “post-condition” steps for each branch, which can get messy.

Yes! We need a way to rejoin Flows after a Condition! In other words: a way to evalulate many Conditions in parallel instead of everything being path dependent. 

E.g., say a Requester has (3) fields: [Department], [Default Agent Group for Tickets], [VIP]. 

1. Every time a Ticket is created, we’d like to set seperate Ticket fields based on these (3) fields from the Requester.
2. We’d like to make a Note on the Ticket depending on their Department, with helpful links for Agents.
3. We’d also like to assign the Agent Group based off the Requester’s [Default Agent Group].
4. Finally, we’d like to raise the Ticket priority if they’re a VIP.  

Right now, I don’t know of a way to run parallel conditions on each of these fields inside (1) Workflow Automator.

Because the Automator run path diverges at each condition, we’d have to make a hierarchy of many Condition blocks after each Condition. Rather, I’d like to be able to split the program run path into (3) parallel paths to make programming and management so much easier! 

​@joelengelhardtcrsrds Until they offer something like a rejoin, while far from elegant, to avoid ending up with highly matrixed workflows, we’ve opted to have multiple smaller workflows.  Effectively a separate workflow for each of the tasks you identified as wanting to perform.  The drawback is we have nearly a hundred workflows currently. But, it does have the benefit (with good naming strategy) that you can easily pinpoint the workflow that needs updating as things change over time.