• Documentation
  • Workato Blog
  • Product Blog
  • Return to Workato
  • Log in
  • ☰
  • Solutions
  • Forums
  • Tickets
New Topic
Discussions Ideas Core Product Features
R

Rinse Gijsman

started a topic almost 2 years ago

Ability to have multiple connection sources to 1 recipe

For Shopify like application. Those apps run the exact same recipes but Shopify kind saas solution may have multiple API credentials. If you maintain two or more domains, Shopify will give you API credentials for each domain. 

1 person likes this idea

Vivek

said almost 2 years ago

Hi Rinse,


I understand you would like to connect to multiple Shopify domains. You can still achieve this by using 'Callable recipes'. If the trigger is from your Shopify accounts, you can have multiple recipes triggered by the different Shopify accounts calling a specific callable recipe. Alternatively, a specific recipe can call different recipes, each connected to a different Shopify account.


Do try this out and let us know. Thank you.

R

Rinse Gijsman

said almost 2 years ago

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..

R

Rinse Gijsman

said almost 2 years ago

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


2 people like this
R

Rinse Gijsman

said almost 2 years ago

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

l

luiz rocha

said over 1 year ago

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. 


2 people like this
R

Rinse Gijsman

said over 1 year ago

Yes @Workato please come with some solution.. 


1 person likes this
Login to post a comment

Still can't find your solution?

Send us a ticket, we will try our best to assist you with your problem

Documentation
Developer's Library
Tutorials
eBooks
Expert Hour
Product Hour
Product Blog
Workato Blog
Product updates
Customer Stories
Workato 2018 © | Privacy | Terms | +1 (844) GO-WORKATO
  • Documentation
  • Workato Blog
  • Product Blog
  • Solutions
  • Forums
  • Tickets
  • Log in
  • Return to Workato