Increased timeout limits for the HTTP Universal Connector!
With our goal of wall-to-wall automation, the HTTP connector presents important ways our customers can connect to any application within their technology stack. In particular, the HTTP connector is one of the most used connectors on the platform, allowing users to easily configure free-form ad-hoc HTTP requests to power their recipes.
We have introduced a new action in the HTTP connector - "Send request and wait for response" - which can now handle requests requiring us to hold connections for up to 1 hour.
This action behaves similarly to long actions in Workato, meaning that the job is suspended whilst Workato waits for the response.
Why is this important?
With the HTTP connector, our primary goal has always been to provide our customers with the most flexible connectivity and ease of use but within the boundaries of what is efficient for our platform. Due to this, we have implemented a timeout of 120 seconds. Oftentimes, this has led to friction with customers when working with legacy APIs, which require long timeouts or when requests that worked with small loads in DEV and TEST started to timeout in PROD with larger loads.
Who can use this? This feature is currently in beta and available upon request. Contact your CSM if you need to test and validate it!