Re: "Case" Branching Logic in Workflows

Hi,

It'd be really helpful if If/Then branches could be based on more than one case. For example, if I want to send a specific email to a contact based a property value, and there are 5 property options, this requires 4 If/then branches. Would be great if one block could manage multiple cases.

Following an if/then branch or the above case branch, would be helpful to be able to rejoin branches so that the remaining blocks do not need to be duplicated for each branch. So, if I just wanted to change 1 email in the above example per a property value, but the rest of the workflow is the same, I could build only one series that applies to all 5 branches.

Thanks!

Shawn

HubSpot updates

10 Replies

Occasional Contributor

Another thought to add - the above scenario could be address by smart content, but I want to report on the different variations of the email separately, since they go to different personas. If smart content emails had separate reported per variation, that would also be helpful.

Occasional Contributor

I was coming in to add this exactly. We have multiple URLs that redirect to a main download page and we need to apply lead sources per URL that we can pull out with manual tagging. I'm currently at 13 if/than statements to capture and apply lead sources. This would be much cleaner if I could apply case statements instead of if/than statements.

Occasional Contributor

This would be very helpful for us. We have alot of workflows that do different things depending on the location our customer is interested in and since we have 7 locations, we need to have 7 levels of an if statement.

Occasional Contributor

I came in to request a solution to the issue of allowing workflows to rejoin branches, or in other words, to have an IF/THEN/EITHER functionality where we could carry on with the workflow in either event so you don't have to create duplicate branches. The use case is whenever you want to perform a check to possibly set a value or something and then carry on with the workflow. If the case model can accomplish that, then this is badly needed. I have come across this use case again and again, and still haven't developed a decent workaround.

Regular Contributor

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