Adding Body Data to Run Service Action Node

Feature requests
1

Hi!

I have made a Service with a Service Endpoint of type POST. I want to run this from an app’s Action using the Run Service Action Node. However, when I attempt this, I get no input options for Request Body Data. I need to run the Service Action bound to the Endpoint based on object ID’s in context in this Action, which is why I need a means of transferring this data.

I have been able to circumvent this issue by using a Web Request Action Node, using the url for the Service End Point. In this Action Node, I can alter the Body Content as needed.

The reason I want to be able to do this using Run Service is that it generally is a more logical approach - why should I not be able to do it this way? Specifically, I would like to be able to right-click my Service Endpoint and “Find References” and actually find the places in my apps this is used. With my current approach the reference is hard-coded into the url of the Web Request.

Hope to hear from you soon,
Alexander

2

Hi Alexander,

Thank you for the explanation of your use case.

The reason this functionality isn’t currently available is that request body input is unstructured data, and there’s no clear definition in our current model for what’s expected as input in a service body. While it’s technically possible to implement, it would require significant development work for what has been considered a relatively niche use case.

However, this will likely be addressed in our upcoming “Flows” concept.

In the meantime, your workaround using the Web Request Action Node is indeed the correct approach, even though it doesn’t provide the reference tracking you’re looking for.

We appreciate your feedback on this, and Flows should solve this pain point more elegantly than trying to retrofit the current service model.

1 Like