Optimizing HTTP Requests for Multi-Client Workflow Implementation

Hello to the entire community,

I am working on a simple workflow for around fifty clients. The data is always the same, so I would like to avoid duplicating HTTP requests.

The idea is to retrieve data via a webhook (e.g., title, video_url, etc.) to create posts on my clients’ social media accounts.

I am looking for a way to share the output data from the “Get a file” HTTP request with all my other clients without having to create 50 different workflows, each making 50 separate HTTP requests via the HTTP module. I also want to avoid creating 50 different routers within the same workflow.

Has anyone encountered a similar situation and could guide me in implementing this scenario ?

Thanks in advance, and have a great afternoon, everyone !

Hi @Mediapole ,

What do you mean ‘data is always the same’ ? Data from which modules exactly ? And in any case if the action to be taken must be instantaneous (user clicks on a button and the post is generated straight away), there might be no simplification of this scenario - other than delaying the answer to the client and storing data in a database for an hour or so, waiting for other clients’ inputs, and then bulk treating the database with another scenario.

Hello @Mediapole,

Not sure if Dynamic Connections will help you, but it requires an Enterprise plan.

If that doesn’t work, you’ll need separate modules for each client’s account, meaning one scenario needs many copies of each of these modules or you need a new scenario for each client.

1 Like