Flow Control: Converger / Merge
not immediately planned
P
Pavel Duras
The Converger module is basically a counterpart of the Router module and it would enable you to merge several routes into one.
-------------------------
When in doubt, please, contact our support (https://www.integromat.com/en/ticket) or feel free to post a question to our Facebook Integromat Community group (https://www.facebook.com/groups/integromat/), where hundreds of specialists, users and fans are willing to help.
Log In
D
Darin Patterson
not immediately planned
We know that there is a great deal of passion among our valued user base on this topic. As we have closely evaluated a solution here, we've had to make very difficult trade-off decisions and, ultimately, we want to be clear and transparent with our customers. This capability is not immediately planned, meaning that the idea is excellent, but it is unlikely that we would be able to deliver it in the next 12 to 18 months. There are three primary reasons for this decision:
- While we fully recognize the high usability benefits of a converger, the vast majority of our customers' use cases can currently be met through the use of best practices in setting and getting variables between multiple routes.
- While we have made some progress on this topic, we've also recognized some significant challenges in implementing this capability, particularly related to edge cases in error handling, incomplete executions, and troubleshooting.
- There are several key underlying capabilities we are alternatively investing in order to open up new things that simply were not possible before.
We know that this news will be disappointing for many users and may not be surprising to others. Of course, we are committed to delivering some of the highest value things on our roadmap to continue to enable our users to innovate at the speed of their ideas. We will commit to continuing to re-evaluate this determination in the future.
Nasiruddin
Pollee Fashion 🌎 small business owners/ Pollee digital market place 🌴 with My Shopify store 🏪 pollee online fashion 👗
Advisore marketing by world Advisor social media with world publisher advisor Nasiruddin from Bangladesh webmail nasiruddinmiah36@gmail.com
Nasiruddin
POLLEE digital Market place 👖 teli1gram with httppollee.wordpress.com
Simon Meggle
As a Python developer, I must say that I am very surprised at the lack of such a converter. When programming, it is the most normal thing in the world to call from function A various functions B1, B2, B3 etc. , which in turn can then call a common function C again.
Without the possibility of merging the flow of the programme in this way, you are condemned to branch out the scenario further and further.
Thomas
There was a time when the only credibly players were Integromat and Zapier but AI is spawning a host of competitors who offer this feature out of the gate. I sincerely hope Make re-assesses this decision now that it's been 24 months since it was first posted.
Tal Spirer
Still cannot believe that Make.com has not yet released something like this, more concerning that it is not even seen as a beyond-high-priority feature that has been long missing and needed!
Tomasz Machura
Honnestly, I am so disapointed. I was looking at Make to automate some processes in my company. I like the UX, the whole experience has just been great.
All our processes are written in BPMN and we use gateways extensively.
For me that was a no brainer that a merge would be available after branching. I was feeling stupid that I couldn't make it work. So I was designing and looking for the module, trying to link branches to a module etc...
How surprised was I to read on multiple forums and tutorials that Make does not have such a vital and basic function as branch merging. Wow - This is such a punch in the face :/
Adam Rogas
...
Rob Hunter
One way of getting round this issue would be to make it easy to duplicate blocks of operations - or allow for "subroutines".
AndyDaSilva52
Rob Hunter: I made a suggestion about the ability to draw a frame, but enable to create a
subroutine
inside a flow is something very interesting.Rory
Rob Hunter: There is an even better way to do this. Create a HTTP webhook, send a JSON payload to a new webhook. This new webhook is connected to the different paths you want to go to, and then you use the webhook responce module to pass back the information you need.
This keeps the main scenario very linear and all of the decisions/routers in sub scenarios which you should never have to look at it if you use good error handling.
Mikuláš Sychra
Rory: Can you please share some scenario (or screen) with this strategy? Do you see some pitfalls here?
I have tried similar way, but Im calling other scenarios, instead of webhooks.
I think it Is better to split one complicated scenario into couple of subroutines, however this Is not possible on free plan and probably can get expensive. Still want to try... :)
Thanks!
Rory
Mikuláš Sychra: So in the first picture there is a module called Deal, Partner or Space. This uses a HTTP request with a JSON payload to send parameters to the webhook in the Scenario called "Space - Partner Deal - Unlimited Deal (opportunity Invoiced)", shown in the second picture.
In the second picture it uses a mixture of the JSON payload and a few modules to decide which way to go down the router. It then gets a certain record based off of this criteria and I have built a JSON payload to send back into the main scenario.
All of the 4 modules have exactly the same JSON payload so that the main scenario knows what parameters are going to come back.
This more or less acts as you own converger, the only negatives are that the JSON payloads passed back into the main scenario need to have the same header body otherwise the main scenario gets confused.
The pit falls of using this method are minor and I make sure to add email error handling in the main scenario incase the subscenario gets a 400 error.
What is your method of calling other scenarios? It sound very similar to this.
Monday Admin
##The Monday_Admin user name above, is our internal login for Monday and Make - we are not affiliated.
This is obviously a financially led decision - which is fine as Make is a business. However business history proves over and over again that companies that move their focus from product first to revenue first always open up a gap in the market for others to fill.
Make is a fantastic product, because it appears to have always been product centric - as this changes, I expect to see other players take advantage of these type of community boards to implement ideas and to gain market share. Disappointed in this decision.
By the way - if anyone ever tells you something will happen in 12-18 months - it will never happen. It seems close enough to be real, but it's far enough away that it will never get any attention. (It will always be 12-18 months away).
D
Darin Patterson
not immediately planned
We know that there is a great deal of passion among our valued user base on this topic. As we have closely evaluated a solution here, we've had to make very difficult trade-off decisions and, ultimately, we want to be clear and transparent with our customers. This capability is not immediately planned, meaning that the idea is excellent, but it is unlikely that we would be able to deliver it in the next 12 to 18 months. There are three primary reasons for this decision:
- While we fully recognize the high usability benefits of a converger, the vast majority of our customers' use cases can currently be met through the use of best practices in setting and getting variables between multiple routes.
- While we have made some progress on this topic, we've also recognized some significant challenges in implementing this capability, particularly related to edge cases in error handling, incomplete executions, and troubleshooting.
- There are several key underlying capabilities we are alternatively investing in order to open up new things that simply were not possible before.
We know that this news will be disappointing for many users and may not be surprising to others. Of course, we are committed to delivering some of the highest value things on our roadmap to continue to enable our users to innovate at the speed of their ideas. We will commit to continuing to re-evaluate this determination in the future.
Jake Spirek
Darin Patterson: Disappointing, but appreciate the transparency. Hopefully it can make it back onto the roadmap!
Denis
Darin Patterson: that’s disappointing. Lucky we as a community can bring in our ideas and vote for it. Thanks for that possibility. But that mean that we also see that the next unplanned item has only a third of the votes in comparison to this one. So that item is highly wanted by the community why do not delivering it? The only point I can see because it’s to difficult to solve, but that can’t be an argument. And the best practice is more kind of a „work around“ than a best practice and 2 of the 5 other planned items have also so called best practices. Postponing it for at least 12 to 18 months is really hard. Please rethink your decision.
Alec Wills
Darin Patterson: The reason there is a lot of passion is because you are ignoring us. Make is a business and that means it needs to make money to survive and thrive. No issue there. However, you ignore your customers at your peril. It is very insulting to say things like "to continue to enable our users to innovate at the speed of their ideas" when we have been promised features like the converger for years without any progress. I for one will continue to move my scenarios off Make until they refocus back on product and off of revenue.
Denis
Darin Patterson: 139 comments and 861 likes and you say no, thats a kick in the ass of your customers.
Chris Power
Darin Patterson: Considering it's been nearly 17 months since you made this comment, I just thought I'd check in and see if there's been any progress. I've been using make for about 2 weeks and I've already run into multiple cases where the lack of this feature causes scenarios to get wildly complicated with a LOT of duplication of modules, requiring lots of extra work keeping them all consistent. This seems like a HUGE gap in functionality and if there are still no imminent plans to implement it, I'd probably go back to looking at other platforms, considering how much trouble it's causing after only two weeks.
Load More
→