Enhancement: HTTP Request Action with Parameter Storage Credentials

Announcements Product News
, ,
1

:sparkles: Description

We are excited to announce a new action version of the HTTP Request action that supports credential usage from Parameter Storage. This action will use credentials created and maintained in SailPoint Parameter Storage.

:information_source: 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 V2 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.

:red_exclamation_mark: 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.

:light_bulb: 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.

:busts_in_silhouette: Who is affected?

Workflows customers. Not available in FedRAMP environments.

:date: Important dates

Sandbox availability: Mar 3, 2026
Production rollout: 3/24/2026 - 4/6/2026

5 Likes
2

They won’t work with year versions? V2025 or /latest?

1 Like
3

This will be very helpful for my workflows with many HTTPRequests included.

Is there future plans to add credential provider functionality to this parameter storage?

4

I have switched an HTTP Request Action to use the new version with Paramter Store credentials - and the Action now fails.

The HTTP Request action is to ISC: PATCH https://myorg.api.identitynow.com/v3/accounts/accountId - where myorg and accountId are shown as valid values in the Workflow execution

The request fails with the error: ‘request failed’ and no output.

This was previously working under the old HTTP Request Action and so I assume it is something I am doing incorrectly in the Parameter Store setup.

Can you advise?

1 Like
5

Hi @Takato, I have a question about this bit.
Currently, if you want to view the definition of a workflow, you must disable it first. You can’t read an enabled workflow through the UI. If we disable it, it is not a running workflow anymore. Can we still enable it afterwards, or will it then complain that it does not work anymore?

Similar question when it comes to minor changes to existing workflows. Can we disable the workflow, make an unrelated change like changing a description, or adding a recipient to a send email action, and then enable it again. Or will it then break due to this new release?

In case of the later, I would argue that we would need a longer time before production roll out as this would be a breaking change which messes with our current way of working. Those in charge to make only minor changes would now not be able to do those anymore until we have updated the workflows to this new way of working, which would take developing time.

Kind regards,
Angelo

6

Really excited for this capability! We are looking to test this one out and find the limits of what is possible :tada:

7

Exactly the point I want to understand as well. Why is the HTTP Request action in workflows restricted to only v3?

The HTTP action is meant to be a generic API call mechanism, so in principle it should support any API endpoint. Limiting it to v3 (for SailPoint specific APIs) feels counterintuitive, especially since many advanced features and capabilities are only exposed on /beta, /v2026, or /latest endpoints.

This restriction could become a major blocker for customers who want to leverage workflows for enhancements on ISC, because it prevents access to newer or experimental API features that are critical for innovation.

How does restricting workflow HTTP actions to v3 align with the published API versioning strategy? Is there a roadmap to extend support for /beta, /v202x and /latest endpoints so workflows can evolve alongside SailPoint’s API ecosystem?

Can someone from SailPoint or @Takato please confirm this?

8

Unclear per usual, but I think they mean v3 of this workflow action:

image
image1458×920 95.5 KB

vs
image
image1922×1024 119 KB

1 Like
9

Tested this with /beta api (*.identitynow.com/beta/accounts) and it’s working as expected.

1 Like
10

We have workflows where an auth is an access_token which is sent in the body of the HTTP Request. In this new feature it is required to select an Authentication Type - whereas in prod this is not a required field - with this new feature our http request does now run.

11

@Takato How can we update our existing workflow HTTP actions to use credentials stored in parameter storage instead of their current configuration?

12

Hi @ruben_elizondo and @Arshad , The “v3” in the announcement is the action version, not the API path and any URL (e.g. /v2025, /latest) works. The action version affects where credentials are stored (in the action vs Parameter Storage).

I’ll make sure we get this updated so it’s clear.

13

Hi Angelo, Thank you for your questions:

  • Disabling a workflow to view it or make minor edits doesn’t change existing HTTP actions.

  • 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 UI will be v3. Existing v2 actions stay v2 and are not converted. Editing workflows via JSON can still add or keep v2 actions.

2 Likes
14

@Arshad you will need to manually update your HTTP actions in the workflow builder.

1 Like
15

Thank you, @patrickboston . We’ll get this updated :slightly_smiling_face:

1 Like
16

Hi @trettkowski we currently do not have plans on our roadmap, but I recommend you submit an idea in the ideas portal if you haven’t done so already.

17

You know it would be nice if the harbor pilot was able to analyze current workflows and either suggest improvements or implement new releases in a side by side comparison format

18

Hi @ady1 , The “v3” in the announcement is the action version, not the API path and any URL (e.g. /v2025, /latest) works. The action version affects where credentials are stored (in the action vs Parameter Storage).

19

@austin_alexander You can submit this to our ideas portal :slightly_smiling_face:

20

Hi @caryharper We are addressing this and I will update the post, but please keep an eye out for our release notes for more details. (I’m assuming “now” was a typo for “not”.)