IF statements is a nice addition, but it is useless if the 2 branches created cannot be reconnected to continue a workflow. Otherwise it just forces us to duplicate all the common events in two branches, once the IF exception is passed...
Hey @troelsfeodor thank you for following up with these details, and yes I can certainly see your use case / goals here.
I am going to merge this thread with the Idea you linked above, this will be beneficial for several reasons:
1. Product Managers will be able to review requests/commentary/context all in one place
2. The votes for both ideas will be combined, and moving forward votes will not be split between similar threads
Hello @troelsfeodor have you tried using IF/THEN branching logic in your workflows? It sounds like this existing branching tool might help you meet your goals.
IF/THEN branches allow you to create two flows in one workflow based on a contact meeting a certain criteria. E.g. IF a contact viewed page X then enroll then in STEP Y / IF NOT then enroll them in STEP Z.
Check out this Knowledge Base Article on how you can use IF/THEN logic and steps in workflows and let me know if this tool meets your needs. If not, can you provide more detail (and examples if possible) of how you would like the workflow tool to perform.
You might also find using Workflow Recipes helpful when building your nurture emails. . These recipes include pre-built with lists, emails, and automation, so you don’t have to worry about setting this up on your own. They are designed to not only help first-time workflow users, but also provide time-saving templates to veteran workflow masters. Once you have installed a recipe, all that is left to do is to customize the assets (e.g. adding IF/THEN branching) and then activate your workflow.
If you have any follow up questions for me / the Product team then just post in your reply.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.