Think manually creating the template string like in my previous post would still have issues with binary files, so adding a more robust solution that leverages the form-data node package now that we can import custom libraries into workflows!
The workflow accepts an array of field or form parts, and uses the package to send the form data customized to whatever the API requires (e.g. a custom part-level Content-Type header). Then the workflow is called from an app with all the necessary fields/files in the payload.
