Proper branching (if/else/elseif) in workflow automation

I really like to see the following feature: tree-like WA. 
 

EG:

Trigger: New deal created. 

[condition] 

if [new deal = stage A: do B, C and D.
 

if [new deal = stage W: do X, Y and Z.

In this case, it would save time and effort of re-creating the automation for the W stage. 

For me personally, it would be a massive time-saver, as I now would have to make 3 different WA for 3 different stages. Plus duplicate that for the three different regions.

Je pense qu'il serait vraiment bien d'avoir la possibilité de donner 2 actions possibles à nos conditions.

Proposer 1 "chemin" si la condition est vrai, un second si elle est fausse.

exemple :

Envoie d'un mail + délai

si "l'email à reçu une réponse" est :

• vrai - alors action : changement d'étape
• faux - alors action : mail relance

We need to request in workflows to have a PATH function, similar of what ZAPIER has to build conditional workflows (https://zapier.com/features/paths), since for example we need to do certain workflows that have different "paths" due to a conditional.

Example:

"We have 4 sales teams and we need to build a workflow to convert into a project based on the leader of each team and assign different activities based on the owner of the deal, so in this case we need to build 4 different workflows. If we only have "conditional" functionality, we can just build only 1 workflow and look for the owner and take the path to do that, similar of what is done in chatbots."

This will help the live of too many people like us that fill out hundreds of workflows in semi-complex situations like this.

I'd really like this too. I can make it work anyway with multiple of automations, but this would greatly simplify things.

E.g. If stage is changed to "2" then "send email template 2", or if it was changed to stage "3" then "send email tempalte 3" etc. It could all be done in one automation.

Hello Guys.

We need a new features in the email automation, it needs more advanced features like Keap. We need if conditions to build 1 automation instead of building many automations to streamline the sales process.

Also, a feature to make the automation could reply to previous thread not send a new email.

The same question.

Is there some estimated time of realising this feature?

They have to add this. The workflows is very weak and i been thinking to move to GHL because of their workflows. You can pause upon reply, have trigger links to start another workflows. and so many other useful features. I love Pipedrive and don't want to change please enhance the workflows it saves us time

I have a big problem. I want to be able to run an automation that allows me to have multiple options dependent on a specific label but currently need to set up 20 automations to do this

What is needed are “If functions” within automations allowing us to build 1 automation flow for all options.

As an example, is if the field option is:

1. X then send an email
2. Y then send a different email
3. Z then set an activity
4. Etc

currently to do this (if you have multiple options within a label or a field) you would need a new automation flow for every option. Quite easily 10 automations for each field/label option.

This problem doubles if I wanted to do this for “new contacts created” and “when a contact is updated. I now need those 10 automations twice, equalling 20 automations.

this seems overkill when a simple “ if function” would allow me to pick different options, depending on what was input.

bringing this up seeing if there is any progress on this, or even taking people out of an automation flow?

I 1000% agree with this.
We have around 100 automations for our company, many just a clone of the original with a slight tweak.
Proper branching would allow us to reduce them to around 20.
It would also allow us to build more complex automations. Thats something we not have done so far, as it would get to confusing to have each branch as a standalone automation.

@Nikolai Sokolov Trust me, changing platforms isn't my preferred option either, but PD really needs to pick up it's development game. Avoiding something and hacking workarounds in 2024 due to lack of development isn't really a long term solution IMO. Especially while others are pouring resources into improving and building additional functionality into their platform. It gives me that feeling that PD is more focused on pocketing cash than developing functionality to keep them competitive. People have been asking for split paths and webhooks for a half of a decade and we still don't have a functioning version of either lol. Ironically I got an email about an hour ago from Pipedrive boasting about their new webhooks that we can't do anything with 😁

@Manuel Oliveira I'd love to bump this as well. It's almost been a year since we heard workflows are being improved but we're all still anxiously waiting. We REALLY need to be able to create more advanced workflows involving branches / split paths and multiple triggers. IMO this should be the #1 priority for Pipedrive's development team. For example, right now we have to have separate automations for "Deal Created In Stage" and "Deal Stage Changed To", and in both English and Spanish. That's 4 automations that should easily be consolidated into one. Or deal won/lost in both English and Spanish - 4 automations required that should be 1. Currently I'd say 80-90% of our automations are just like this.

1. No branches / split paths or multiple triggers makes managing the workflows a confusing nightmare
2. The limited number of workflows you can have in an account based on how they currently operate should be criminal 😂
3. (Off Topic) - The 10 action limit per workflow being increased would be nice. We use workflows to build cadences that involve calls, emails and SMS's. New lead → create call attempt 1, once it's marked complete & no deal created, automate an email, SMS, and create call attempt 2 activity, so on and so forth. That's 4 actions and a lead has only received 1 call attempt.

I know every Pipedrive user would really appreciate, and benefit tremendously, by improving the workflows. I'm sure there are other good examples out there, but I'd suggest taking a look at GoHighLevel's workflows which are the best I've seen. The flexibility their provides allows users to build for nearly infinite scenarios. This would be a MONUMENTAL improvement for Pipedrive. Any time I've recommended Pipedrive to someone, their biggest reason for not sticking with it has been the workflows.