Enhancement: HTTP Request Action with Parameter Storage Credentials

Description

We are excited to announce a new version of the HTTP Request action that supports credential usage from Parameter Storage. This action will use credentials created and maintained in the SPS Parameter Storage. All running workflows with existing HTTP Request action will continue to run, new workflows with the HTTP Request action will only support V3 and the Parameter Storage.

What You Need to Know

• “V3” is the action version, not the API path.
• Existing HTTP Action v2 instances in your workflows keep working and continue to use their current configuration.
• Any new HTTP Request action you add in the Workflow Builder UI will be V3. Existing V3 actions stay V2 and are not converted.
• Disabling a workflow to view it or make minor edits does not change existing HTTP actions.
• There is currently no HTTP Action V2 deprecation policy. We will communicate any future deprecation and timeline in advance.

Problem

Managing secrets and configuration values across multiple actions is a challenge, as it requires repeatedly entering the same information, which is inefficient and prone to error. This manual process not only introduces security risks when handling sensitive data but also makes it difficult to ensure that all instances of a value are consistently updated.

Solution

This feature adds three main value drivers for customers.

1. Centralized Management: A single point of management for credentials used in HTTP Request actions.
2. Reduced Duplication: It enables customers to use the same credential for the same external or internal systems.
3. Seamless Updates: It allows customers to change parameters/credentials without affecting the running/enabled workflow. 

Who is affected?

Workflows customers. Not available in FedRAMP environments.

Important dates

Sandbox availability: Mar 3, 2026
Production rollout: 3/10/2026 - 3/31/2026

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