topic Re: multiple HTTP connection endpoints within 1 recipe in Workato Pros Discussion Board

multiple HTTP connection endpoints within 1 recipe

shruti-2-sharma — Fri, 25 Feb 2022 19:30:48 GMT

I am trying to create recipe to call more than 1 http connector.

But facing issue while using multiple HTTP connection endpoints within 1 recipe.

only one connection work at a time.

please suggest me how to do it.

Thanks in advance

Re: multiple HTTP connection endpoints within 1 recipe

roland-daane — Fri, 25 Feb 2022 19:34:40 GMT

Whats the issue?
I have recipes the have multiple http connectors to different systems like Bim360, Sharepoint and Forge

Re: multiple HTTP connection endpoints within 1 recipe

a-muthiah — Fri, 25 Feb 2022 19:36:07 GMT

Classification: Confidential

You can use a secondary connector

https://docs.workato.com/features/secondary-connectors.html#how-to-use-a-secondary-connector-on-workato

Thanks,

Muthiah

Re: multiple HTTP connection endpoints within 1 recipe

james-ng — Fri, 25 Feb 2022 19:37:30 GMT

how about calling another recipe with the second http connector?

Re: multiple HTTP connection endpoints within 1 recipe

max-knutsson — Fri, 25 Feb 2022 19:46:34 GMT

the second http connector should help. Unless you need more than 2 in one Recipe

Re: multiple HTTP connection endpoints within 1 recipe

shruti-2-sharma — Fri, 25 Feb 2022 19:52:22 GMT

I need to invoke 5 api . so , need to create 5-http connection .Is there any way to do that

Re: multiple HTTP connection endpoints within 1 recipe

jblanchett — Fri, 25 Feb 2022 20:11:59 GMT

You can use the HTTP and HTTP Secondary connections to support 2 separate systems. Keep in mind that you can store the base URLs and auth credentials in the connection and hit different endpoints within each action by appending to the base URL.

If you truly need to hit 5 different base URLs, you might consider breaking your recipe into multiple recipes by leveraging callable recipes. Alternatively, you can use an empty HTTP connection as a shell and set the base URLs and authentication within each action. I am NOT recommending you hard-code auth creds in your actions, that’s bad practice, but you can fill those in via other ways depending on the auth mechanism, such global property variables or calls to synchronous callable recipes to get oauth tokens.

Re: multiple HTTP connection endpoints within 1 recipe

max-knutsson — Fri, 25 Feb 2022 20:14:59 GMT

So all of these are totally different systems/APIs?

If answer is Yes, then I see 2 options

1. Use a callable function (go to next step => search callable recipe by workato) because if using callable function you will not hit the HTTP connector limit, basically you can have as many callables as you want.

a) Create a callable function for API 1 - use whatever authentication method required for this API, create parameters that you need to push to this callable recipe, call the API then return the result back to the MAIN recipe

b) repeat the same steps 4 more times until you have 5 callable functions, each calling their own api, accepting their own Parameters and return Result

2. Second option is to use HTTP to 5 different APIs but create a "generic" http connector which has "Authentication" NONE and authentication using HTTP headers manually for each call. This will be messy as its not very reusable. For reusability/Best practice I recommend option 1, use this option only as last resort, as pointed out by Joseph above.

Re: multiple HTTP connection endpoints within 1 recipe

vinny-sosa — Fri, 25 Feb 2022 20:47:32 GMT

This is one of the reasons why some apps have a 2 designation. Like Marketo and Marketo 2. So you can use different connections for each.

If there isn’t a duplicate connector available you might consider using a custom auth and custom http setup.

Another way to do this is to use a callable recipe so you can have different auth in each recipe even though they are using the same connector.

Re: multiple HTTP connection endpoints within 1 recipe

mroldanvega — Fri, 25 Feb 2022 21:31:07 GMT

A third option could be to set a generic http connector with not authorization. This way you can configure all the different endpoints within the recipe with a single connector, BUT it depends on the type of authorization each endpoint users. This is not ideal, or a best practice, but just a workaround for the time being.

Re: multiple HTTP connection endpoints within 1 recipe

rayudu_addagarl — Fri, 25 Feb 2022 22:35:38 GMT

Another option of your API supports graphql , and its same system one could get better results without multiple calls to end points.

As always there are tradeoffs of usine one vs other

Since GraphQL substantially reduces the number of endpoints, services can acquire all the needed data with one call and can format this information inJSONfor fast retrieval. GraphQL is alsotransport-layeragnostic, so the API server can exchange data over any protocol, including HTTP, HTTPS and WebSockets, and TCP.

A head-to-head GraphQL vs. REST performance faceoff (techtarget.com)

Re: multiple HTTP connection endpoints within 1 recipe

levajar — Wed, 12 Apr 2023 13:12:00 GMT

Love this community discussions with ideas of calling multiple http endpoints within a single recipe.

If we have someone built a community recipe template - probably that will add more value as well for folks to refer it.