We've enriched the HTTP(S) step in next-gen actions with dynamic values possibilities. Just drag the HTTP(S) step on your canvas and try it out!
Dynamic values
From now on, you can easily configure your HTTP(S) step by using dynamic values in your URL and body. With this improvement, you no longer need to use expression steps to transform the variables to a functional format. This gives you a lot of flexibility to configure the HTTP(S) step to your liking.
Just drag the HTTP(S) function on your canvas and try it out! Read through this article to find out how.
Coming soon
Soon, we will add the ability to select a newly created schema model and output type to structure your output response. This way, you don't need to build extra action steps to establish a functional request to an API or remote data source.
That was all for now. Your feedback allows us to continuously improve the product. So please, let us know what you think about it!
