Blog

Enhancement: Smarter Output Handling for HTTP Request (POST)

Author

  • Sesche2

    SailPoint

Description

Workflows now automatically trims HTTP POST request outputs when passed into a loop, keeping only the fields you reference in later steps. This extends the payload trimming already available for GET requests—delivering smaller payloads and faster execution times with absolutely no changes required to your existing workflows.

Problem

POST responses can be large, especially inside loops. Storing the full payload after every iteration adds overhead and clutters execution history when you only need a few fields downstream.

Solution

  • Automatic trimming: Loop inputs from POST steps keep only referenced fields.
  • Better performance: Less data stored and transferred per run.
  • Full output in test: Inspect all response fields while building, same as GET trimming today.

Who is affected

Workflows customers using HTTP Request (POST) whose output feeds a loop. No action is required.

Important Dates:

Sandbox Availability: Jul 20, 2026 - Aug 7, 2026

Production Rollout: Aug 10, 2026 - Aug 31, 2026

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