Segment or split an automation into different paths
I would really like the ability to split an automation into different paths. Each path would run based on different filters and conditions. Please add to your list of ideas to implement
Comments
-
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
0 -
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.
1 -
What do you think about this guys?
0 -
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.
0 -
I'm not 100% but I think this may be in the works Rodrigo. Got a feeling they mentioned conditional paths in workflow automations during the last webinar. I could be wrong though.
0 -
Hi everyone, there is something along these lines being worked on. I will be sure to gather community feedback in one post so the product team can go over it.
1 -
Hello all!
It is now Februaey 2024. Does anyone know if there has been an update om the workflow path issue?
0 -
The same question.
Is there some estimated time of realising this feature?
0 -
This really is an absolute must especially considering the limits to the number of workflows you can have. Not being able to do paths, being limited to only one trigger per workflow, IE needing 2 workflows for 'deal created in stage' vs 'deal updated in stage' or requiring separate workflows for the same field being changed whether it's a lead or a deal requires a lot of extra management of workflows. Now imagine that for multi-lingual workflows, it's brutal.
Other platforms are constantly rolling out new features and it seems like the development at Pipedrive has reached a stand-still. While I really like Pipedrive, it is rather discouraging that development, if any, seems to be going at an alarmingly slow pace.
0 -
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
1 -
We actually use GHL too and have been considering switching over completely. When we first started GHL was missing some core functionality we needed so we decided to tie in Pipedrive but GHL has come a long way and continues to improve.
We really prefer the UI in Pipedrive for the agents and don’t want to switch but as we grow, automations become an even more integral part of our business and PD just has so many limitations. So end of the day, like Ahmed said, please improve the workflows :)
0 -
Hi @Manuel Oliveira , please escalate this to the team - very essential feature of workflow automations. HubSpot nailed it with three different variations for branching, making it easy to design complex workflows. Currently, the limitation of just one conditional makes workflow automations super limited and we always switch to make for anything more complex than a 2-step automation. Given the webhooks in automations are unusable currently (the admin permission fiasco), workflow automations are the last thing we mention to clients or touch in the setups because they are just very, very limited.
0 -
@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.
- No branches / split paths or multiple triggers makes managing the workflows a confusing nightmare
- The limited number of workflows you can have in an account based on how they currently operate should be criminal 😂
- (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.
0 -
@wonders for the time being, one workaround to consolidate deals matching several other criteria for the trigger, use the filter option. general idea:
- create a deal filter that scopes by several conditions, i.e. english and spanish deals
- in the instant condition section of the automation, use filter option in conditions
this will effectively check wether the deal matches the filter or not, which in turn can have complex matching handled.
@Manuel Oliveira can you please remind wether the matches filter triggers only once? Can't find documentation on that, but remember vaguely that the match filter only triggers when the deal enters a filter for the first time.
0 -
@Nikolai Sokolov I appreciate the suggestion and I'll definitely see if there's anything I can consolidate. We do use the matches filter option in Zapier for a few things but that is the trigger itself. It appears that in Pipedrive the filter has to be triggered by a deal updated or a deal created etc though right? I need to consolidate those triggers into one! :)
Say I want to trigger a series of emails for customers that either are created in stage X, or moved to stage X. If I create a filter, how can I trigger off of both of those? I guess that is a great question if it'll filter only once. For example, say a customer enters the workflow through that filter, I send email 1, now I add a wait. After the wait, I want to check if the customer is still in stage X and send email 2. Will that filter still pass?
Ultimately the biggest short coming for us is the lack of paths. For example, workflows involving language - we can get both languages to trigger, but we want to send automated emails or SMS's in the customers native language. So instead of doing paths, we have two identical workflow triggers but with two different language conditions.
I'll be interested in seeing if that filter only triggers once. I'll try to test it out today if I get a chance.
0
