Enhancement: Smarter Output Handling for HTTP Request (GET)

Announcements Product News
, ,
1

Description

When you use the HTTP Request action with the GET method and a JSON response, Workflows now keeps only the response data needed by later steps. This helps workflows run more efficiently while still giving you full response visibility during testing.

Problem

HTTP GET calls can return large JSON payloads, but most workflows only use a few fields. Keeping the full response for every run can add unnecessary processing overhead, especially in workflows with loops.

Solution

  • When using the GET method for HTTP Requests, Workflows automatically keeps only the fields referenced in downstream steps.

  • This reduces stored output size and improves workflow efficiency.

  • In Test Workflows, the full response is still shown so admins can inspect available fields and map paths confidently.

Who is affected

Customers building workflows that use the HTTP Request action with the GET method.

Important Dates

Sandbox Availability: Jun 3, 2026 - Jun 8, 2026

Production Rollout: Jun 17, 2026 - Jul 1, 2026

2

Hi @Takato,

How would the workflow know which steps are being required later? Does it use an elementary regex to see which fields are being called?
For example, If I use dynamical references like $.hTTPRequest.{{$.trigger.requiredField}}, will the HTTP Action know to keep the value mentioned in the trigger? Will this dynamical functionality keep working after this update, or will this update break all workflows that rely on dynamical references?

3

Hey @angelo_mekenkamp , dynamic paths are supported and continue to work as it does today. Without going into too many details, a workflow will know at the start of the execution which steps are being required later.