JUL 01, 2024 | Node outcomes & advanced settings: Web request

Angel Cheung
Angel Cheung
  • Updated

This release includes the following features and improvements. 

Release 20240701

Node outcomes for Web request

web request node outcomes.png

You can personalise experiences based on the outcome of a Make a Web Request node.

For instance, if a web request encounters a 404 error, you can continue experiences on the 'Failed' path to notify a staff member, or take an alternate action instead.

Learn more about Web request outcomes.

Navigate to the Outcomes tab in the Make a Web Request node to learn more about 'Success' and the optional 'Failed' path.


The experience will continue on this path if the web request response is accepted with a 2xx status code.


The experience will end if the web request response encounters client errors (4xx), server errors (5xx), or unsupported formats. You can enable the "Path" option to handle failures within the flow.


Advanced request preferences for Web requests

web request advanced tab.png

You can now customise how a web request should behave in the event of a redirect or timeout. These advanced settings ensure your web requests are handled efficiently and securely, providing greater control over how HTTP requests are processed within your flows.

Navigate to the Advanced tab in the Make a web request node to discover more about these settings. Learn more about Advanced settings here

Follow redirects

Allow requests to follow HTTP 3xx requests for a maximum of 10 redirects. This is useful for accessing requested resources that have moved to a new URL.


Wait for 100 seconds (configurable up to 360 seconds) for a response from the server before timing out. Adjust this setting if you require a longer or shorter wait time depending on the service you are interacting with.

Bug fixes & improvements

  • Merge field validation now works in Web request and Outbound email bodies
  • Merge field validation now presents merge fields that do not exist as errors