Proper branching (if/else/elseif) in workflow automation
Comments
-
@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 -
Hi, I'm new to PipeDrive. Was very excited about working with it, but I just learned about the lack of an IF/ELSE option in any automation. Some of our automations are complex trees full of conditional branches. I'm dreading having to work with a 3rd party service since this seems like another potential place for errors.
Will the if/else feature be added to Pipedrive?0 -
Hi @ma_wove while this might take a long minute for pipedrive to integrate, I can strongly suggest the webhook to make/zapier way. It was a gamechanger on our projects, especially since other limitations of workflow automations still make it difficult to build complex logic in pipedrive.
The idea is this: build a very focused condition for leads/deals/contacts/orgs to enter the automation, send an id to webhook of make/zapier, do whatever you want there.
Since both make and zapier offer the widest integration with myriads of tools, its very convenient. They also have robust error catching and are super easy to maintain.
1 -
Thank you @Nikolai Sokolov! I'll give it a try.
0 -
Hi @Manuel Oliveira any news on this? In terms features, Pipedrive is left in the dust by other CRM and I'm sure you'll agree. Look at all the hacks and hoola hoops the users has to do in order to become efficient in Pipedrive. In the end people are loosing more time and money using Pipedrive.
If only data migration is easy and less costly I would already be in a happy place (that is with hubspot).
It's hard to grow with Pipedrive. There is just so many limitations.
1 -
I have started implementing these flows in one of Make/Integromat or Zapier or Relay.app.
1 -
Thanks @Amit Sarda (AmitSarda.xyz) I was actually thinking of doing the same with Make/Integromat.
0 -
@Randall Pena I couldn't agree more. We're on the brink of leaving Pipedrive as painful as it may be to migrate the data. At some point we need to pull the band-aid off. As our business grows we're in the same boat having to implement more and more hacks for very rudimentary tasks. Our business is beginning to feel like it's held together by duct-tape. While Make and Zapier may be able to handle some of the short comings, having to create more integrations to handle basic operations feels like we're slapping more tape on. Over the last few years we've remained hopeful that improvements were coming, but at this point I think it's pretty clear that Pipedrive is no longer actively developing it's platform in an effort to be competitive with other CRMs.
You said it best, people are losing time and money with Pipedrive. That's us.
1 -
Hi @wonders I think make/zapier is an essential part of any CRM setup. We do both HubSpot and pipedrive setups and end up using make with both - there's just no way around it. While it is true that HubSpot has a better automation suite with more capabilities, we still end up using make for whatever HubSpot can't handle internally.
While I do agree that simple branching is essential, handling stuff with make became really straightforward since webhooks has been introduced. Financially, it's actually still cheaper to do pipedrive + make than HubSpot + make, simply because HubSpot is much, much more expensive.
So I disagree with the statement of make = duct tape. It's more of a "automation in 2024".
That being said, I'd really welcome branching in pipedrive :)
1 -
To be fair, the automated webhook did relieve a lot of frustrations on my part. I didn't realize until now that Make/Zapier is indispensable to any CRM setup.
Thanks for that perspective @Nikolai Sokolov, it somehow eased up my grievance.
And yes, branching within Pipedrive is still something we all need, it's a basic and essential feature of a workflow automation. It simplify things and lessens our costs.
Also increasing the 10 actions limit per workflow would be a big help.
It would be in Pipedrive's best interest to pack more value to their CRM at an affordable price, that's how they get a giant market share and beat their competition.
0 -
While Make/Zapier may be essential for integrations between other platforms and the CRM, it shouldn't need to be used to perform tasks that should be handled by the CRM. The fact remains that Pipedrive has quite a few shortcomings that other established and actively developed CRMs don't have. And very basic functionality at that.
For example, there's no way to view all leads for a contact. You can only see open leads. The ONLY way to get to a previously archived lead from a contact is by searching for it in the search bar. Now as a high volume company, imagine having 17 John Smiths, each of which could have several leads, and now your agent needs to find the notes related to the previously archived leads to understand the customers situation better. You search "John Smith" and 100 of them come up with no email, no phone number, no status (you don't know if it's opened or archived). That's just one nuance related to leads, there are 1,000.
The workflow automation needs a complete overhaul. Even just getting access to the fields of connected objects is brutal having to hack it with some assigning of "Linked Person to the Linked Person" etc. I may expect the MVP approach from a new CRM, but I expect a lot more out of Pipedrive.
No perfect solution exists, and no company has every feature. But what's alarming to me is that suggestions pour into the community boards and many have been a huge concern for many users for years on end but have yet to be implemented. The zip code for address fields and branching are prime examples. The important thing is to keep moving forward, and sometimes it feels like the Pipedrive train is at a stand still. Pipedrive is established enough and has enough integrations, with more functionality they could easily increase the price and have no trouble getting it.
0 -
Hi @Nikolai Sokolov, @ma_wove, @wonders, @Kevinraybor, @Michael Wallenwein,
I'm Jess and I'm a product manager in the workflow automations team. I appreciate that this is an old thread, but we are currently in the research phase to implement branching in Q2 this year.
I'm looking to interview a few people to get a better understanding of the requirements and get some feedback on early prototypes.
Would you be interested in having a quick chat to share your insights? Calls are taking place next week (10-12 Feb) and take about 30-40 mins.
You can book a slot with 👉️ this link 👈️ (link has been disabled as all the slots are full, but if you want to be involved in future testing please reach out to me here or at jessica.stacey@pipedrive.com)
Many thanks!
Jess1 -
Hi there 👋
I'm Jess and I'm a product manager in the workflow automations team. I appreciate that this is an old thread, but we are currently in the research phase to implement branching in Q2 this year.
I'm looking to interview a few people to get a better understanding of the requirements and get some feedback on early prototypes.
Would you be interested in having a quick chat to share your insights? Calls are taking place next week (10-12 Feb) and take about 30-40 mins.
You can book a slot with 👉️ this link 👈️ (link has been disabled as all the slots are full, but if you want to be involved in future testing please reach out to me here or at jessica.stacey@pipedrive.com)
Many thanks!
Jess
1 -
Amazing news, scheduled a call
1 -
Hi @Jess Stacey,
appreciate the effort 🙏 I booked a slot.
Thank you1
