Hello Developers, I was going through the Workflow documentation but couldn’t find any sample related to HTTP action. Can anyone please share the sample workflows for the “HTTP Request” action? Thank you, Subash

The HTTP Request action has undergone a major update. Some of the information in this solution may no longer be valid. Hi @schouhan , There’s some non-intuitive quirks to the HTTP request action in beta Workflows, some of which may be inadequate for your needs. The workflows team is working on…

[image] Colin McKibben: his proves problematic for post bodies (or any other parameter for that matter) where you need to construct a complicated JSON string from several variables in the data model. Unless your post body is a static string literal, or you can create the post body from a single …

Variable insertion is on the roadmap, but it won’t be available this quarter. I don’t have a firm date on when this will be added.

Hello @colin_mckibben thanks for your reply. So there is a workaround to this? As prerequisite, we will need to perform a HTTP action with a JSON body like: {“u_contracttype”:"$.trigger.attributes.sfId",“u_costcenter”:"$.trigger.attributes.endDate",“Xu_employeecategory”:"$.trigger.attributes.sfId"} …

Unfortunately, there is no way to accomplish what you are trying to do as of today, but it will be supported in a future release of Workflows. For now, you can only use a string with no variables, or a single variable defined in JSONpath. There is no in-between.

Hi @colin_mckibben ! As workaround we are trying to definyng the body on a previus step, send email type. We are trying to call the body on the HTTP request step as variable but we can’t. If I remember well, we can send information from one step to another, something change? it’s a new tech limitati…

Hi @Beatriz , I’m don’t recall if Send Email ever had an output. I tested on my end and can confirm that send email doesn’t return any variables that can be used in subsequent actions, so you can’t craft the HTTP body using a previous Send Email template.

Hello @colin_mckibben , Yes, the Send Email step doesnt return any value. As an alternative we are going to send by email the body that we wanted initially sent using an HTTP request step. The issue we are facing now is that one week ago, we were able to send a body with the information calculated o…

@Beatriz , I’m not sure what changed, but looking at your code it appears you context value is no longer valid. The context should be a simple JSONpath, like $, and then you can use JSONpath to reference individual variables in your body. Please see below for an example that works in my environmen…

I also hope we’ll be able to use the same variables when they come out in the URL field and not just the body. I would think this would work similar to the way the email template works.

Hi @colin_mckibben , Any timelines for release of the variable insertion within the HTTP workflow step? Thanks!

HTTP Request Action Workflow

SailPoint Human Fabric (SHF) SHF Discussion and Questions

mikeburns365 (Mike Burns) January 31, 2023, 2:09am 14

Looks like it possible now

Topic		Replies	Views
Workflows: How to dynamically create request body in HTTP action SHF Discussion and Questions workflows , identity-security-cloud	11	2380	July 5, 2023
HTTP Action in Workflows SHF Discussion and Questions workflows , identity-security-cloud	6	1577	July 3, 2023
Inline variables not resolved in body for http request action SHF Discussion and Questions workflows , identity-security-cloud	2	521	November 29, 2023
Http request workflow variable issue SHF Discussion and Questions identity-security-cloud	1	116	June 26, 2025
"HTTP request" workflow SHF Discussion and Questions workflows , identity-security-cloud	13	806	December 12, 2024

HTTP Request Action Workflow

Related topics