Follow HTTP 302 Redirects in Send HTTP Request Action

[yuri]

Hi,

Will be added with a config parameter set to false by default. To prevent SSRF, we will need to implement checking each redirect host. Once it's done, we can enable redirects by default.

[erykjakubik]

Hi,

I'd like to request support for following HTTP redirects (302) in the **Send HTTP Request** action in both Workflows and BPM.


Current behavior
When a Send HTTP Request action receives a 302 redirect response, the process fails with the following error:

[2026-03-14 18:53:58] ERROR: (302) Process 69b5aec33ac761d87, element 69b5aec3414b5bd91: Workflow: Send Request action: 302 response. :: /var/www/html/custom/Espo/Modules/Advanced/Core/Workflow/Actions/SendRequest.php(174)

Expected behavior
The HTTP client should follow the redirect automatically (similar to curl's `-L` flag) and return the final response body.

Use case

I'm integrating EspoCRM with **Google Apps Script Web Apps**, which are a popular and free way to interact with Google Workspace APIs (Google Drive, Sheets, Gmail, etc.) without managing OAuth tokens manually.


Thank you for considering this!