Current Workaround:

To meet our project delivery timelines, we are temporarily proceeding with displaying the API responses in the workflow UI. While this allows the workflow to function, it is not an ideal or long-term solution, as it contradicts our UI and security requirements.

Feature Request:

We request an enhancement that allows:

• API responses to be fully hidden or suppressed from the user interface, while

• Still enabling the workflow to:

• Parse and evaluate API response values, and

• Conditionally move forward to the next step or branch within the same workflow.

Possible approaches (for consideration) could include:

• A “Hide API Response” or “Suppress Output” configuration option.

• The ability to mark API responses as internal-only, accessible only for workflow logic and not UI display.

Business Impact:

Implementing this feature would:

• Improve security by preventing unnecessary exposure of API data.

• Enhance end-user experience by reducing UI noise.

• Enable cleaner, more controlled workflow designs.

• Eliminate the need for workarounds in production environments.

We believe this enhancement would benefit not only our team but also other customers with similar automation patterns.

Thank you for considering this request. We would be happy to provide additional details or examples if required.

We would like to submit a feature request related to API-based steps within Harness workflows.

Background / Current Use Case:

In our current workflows, we invoke APIs as part of a step and receive responses from those APIs. Based on specific values or conditions in the API response, we programmatically decide whether to move forward to a subsequent step within the same workflow or branch to a different step.

This conditional flow control is a critical part of our automation logic, and it works correctly when the API response is displayed.

Current Limitation:

At present, Harness requires that the API response be displayed in the workflow UI in order to:

• Access the response values, and

• Proceed to the next step in the workflow based on those values.

However, there is no option to fully hide or suppress the API response output while still allowing the workflow to evaluate the response and move forward conditionally.

Problem Statement:

There are scenarios where:

• API responses may contain sensitive, verbose, or internal data.

• Exposing full API responses to end users is not desirable from a security, usability, or user experience standpoint.

Currently, if we attempt to not display the API response, the workflow does not allow progression to the subsequent step, which blocks our implementation.