Have you ever used a descending if/then branch in a workflow? 🤔 This week's #1MinuteHubSpotTip 💡 explains how this strategy can be leveraged to check between outcomes in your automation.
Using workflows to automate your sales operations can be a game changer for your business.
Hey LinkedIn, it's Liam Redding, Senior HubSpot Strategist with Remotish Agency, and I'm back again today with another one minute HubSpot tip.
Today's tip is about descending if/then branches. So we can see this workflow uses a series of if/then branches that descend downward, and check different outcomes. So this can be used for a variety of use cases, but this is just one example of that. It's not a perfect example, but it does work.
So in this example, Products is known and Became a Customer data is less than one day ago, that triggers the contact to come down. Now the purpose of the workflow is to check between all the outcomes that could occur for products. So it could be product one, product two, product three, or because it's a multiple checkbox property, it can be a combination of those things. So each if/then branch checks for every product, and each product gets its own if/then branch. So this is for product one. If that's true, the product is any product one, we will enroll them in the onboarding related to that product. If not, we'll go down an unmet branch, go to action, then we'll check for product two.
If that's true, we'll do the same thing that we did for product one to product two, none met, we'll go to action, we'll come back to product three, we'll do the same thing. As you can see, this is a three step process, but you can make a very long descending if/then branch that checks for outcomes or whatever you need it to do. It's an interesting concept. So please let me know your thoughts in the comments below how you can see this being useful. And I will be back next week for another one minute and 30-second HubSpot tip.