Hi!
I miss the ability to set body content in Run Service action node.
Having to use JavaScript with fetch is not optimal if one wants to read the response into a runtime data source.
Marcus
Hi,
Thank you for the feedback. I agree that this could be simpler.
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.
However, this will likely be addressed in our upcoming “Flows” concept.
In the meantime, a workaround is using the Web Request Action Node and map the data with the Result Parser.
Flows should solve this pain point more elegantly than trying to retrofit the current service model.
// Erik
Hi Erik,
That works, it would be nice to be able to set unstructured body data on a service call, although I do not know about the upcoming “Flows” concept, so maybe that would be a better solution.
The biggest problem with a web request action node, is that it does not hold the reference in the same way, so it allows for deleting endpoints that are in use.
Marcus