When processing data from webhooks, I use sequential processing because parallel processing often results in exceeding API limits. However, I notice that sequential processing is quite slow, and I would like to speed up this process by 2x. Therefore, I want to know if there is a way to set the number of simultaneous processing threads for webhook data or somehow speed up the sequential processing.
So the bottleneck is not Make, but the external service?
There’s not much you can do about it except maybe route it through two separate connections to two separate accounts.
Hope this helps! Let me know if there are any further questions or issues.
— @samliew
Hello @sprt; when we need data returned, we’ll use Make’s Webhooks and Webhook response modules.
However, when no data response is required, I love Make’s On Demand functionality using Make module Run Scenario. It bypasses the webhook connection delays and is an authenticated request to run a scenario. And you can pass configuration information too.
Within your targeted scenario, you could put throttling into place as needed.
At Axelerant, we use a Make Webhook to monitor Slack events and engage our conversational chatbot when needed via Make Run Scenario.
1 Like