# "Case" Branching Logic in Workflows

**URL:** <https://community.hubspot.com/t/case-branching-logic-in-workflows/8076>\
**Category:** HubSpot Ideas\
**Tags:** workflows\
**Created:** [March 9, 2018, 4:12pm UTC](https://community.hubspot.com/t/case-branching-logic-in-workflows/8076 "2018-03-09T16:12:59Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![DevinRZC\_DM](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/devinrzc_dm/32/30191_2.png) [@DevinRZC\_DM](https://community.hubspot.com/u/DevinRZC_DM)\
**Post date:** [July 15, 2019, 5:57pm UTC](https://community.hubspot.com/t/case-branching-logic-in-workflows/8076/6 "2019-07-15T17:57:31Z")

</div>

I really love this idea! Previously, I voted for the option to clone branches within workflows but this seems like it would allow an additional level of simplicity even if it requires a bit of a different breakout that just an if/then branch. It would be cool if HubSpot combined or consider these votes with the votes here to find a great solution and help it carry some weight since it’s a very time consuming issue. [https://community.hubspot.com/t5/HubSpot-Ideas/Clone-branches-within-a-workflow/idi-p/17453](https://community.hubspot.com/t5/HubSpot-Ideas/Clone-branches-within-a-workflow/idi-p/17453)

---

_[View the full topic](https://community.hubspot.com/t/case-branching-logic-in-workflows/8076)._
