Blog

Enhancement: Smarter Output Handling for HTTP Request (GET)

Author

  • Sesche2

    SailPoint

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

To ask questions and learn more please visit the Developer Community.