Ability to have multiple connection sources to 1 recipe

Hi Vivek, 

I understand that it would be possible.. But we have so much to map.. It doesn't make sense, why should it be a problem to use 1 and the same recipe for 10 different credentials, why should it be an issue? I don't get it.. 

I know there are workaround, but this cause a lot of more work..

Today I ran into another challenge. 

I do have 1 transaction source, I get transactions from 1 source. Based on some values we need to decide to where we post data we have:
1. Multiple connections to post the same data
2. Multiple connection to post different data

for 1: lets say I would like to post shipping confirmation to both my ERP and the sales channel (shopify). Both connections working HTTP, how to use multiple HTTP connection endpoints within 1 recipe? I know callable recipe would, but that way you keep getting to much maintenance and possible errors.

for 2: let say I have 10 shopify stores, this means that based on some identifier I have to decide to which Shopify I would like to post data. This can be done by trigger filtering, however this means that we have to get 10 different recipes to handle 1 transaction flow. Again maintenance will be little more complicated and total intergration will be looking like a spaghetti soup.

We really like to get 1 type of transaction within 1 recipe for debugging and to keep everything simple. Integration is already difficult enough.

thanks

I would like to schedule a call regarding this enhancement, for my point of view this should be developed. 

I'm surprised that this is being ignored. I'm with you, Rinse. 

Stumbled upon this issue within 15 minutes of testing Workato.

Overall, the product is very good, but this and not being able to test steps individually are serious productivity bombs. 

Yes @Workato please come with some solution..