Not really at the moment – although there is now an enhancement ticket to improve the Multipart Read so that it could do things like this. I’ll try and keep you updated about when it goes into development.
For now, another option would be to write the file to a “temporary” location and then have a separate pipeline that moves the pipeline to the final location. Then the API would require two POST calls, one to upload the file and the other that would take the file path and other things needed to write it to the final location that would “commit” the file.
let us know such updates.
however, as you said we can write file to temp location like sldb, even for that we would require some parameter name to map as the filename.
Ex: the pipeline you shared is writing file as attachment.txt, not the name of the actual sent attachment, how this can be handled if the name of file need to be the same in post request?
Also, I tried with making task as ultra and pass parameter, ultra is not capturing the parameter in triggers
