@Craig Darnley Thanks for reaching out. It is more about what is the right way your endpoint accepts the body and header. Have you tried to create the request using fiddler or postman to test it to confirm if the file is created correctly? Once you have validated with fiddler/postman then it would be easy to troubleshoot it from the HTTP action end whether the request is formed correctly or not.
Please share the request details from the postman/fiddler end. There are some limitations from HTTP connector end as documented here with the Omitted HTTP headers but as per your request I don't see any.
Further you try to use the JSON object in the body as documented here and see if it resolves the issue.
To handle content that has
multipart/form-data
type in HTTP requests, you can add a JSON object that includes the$content-type
and$multipart
attributes to the HTTP request's body by using this format.
"body": {
"$content-type": "multipart/form-data",
"$multipart": [
{
"body": "<output-from-trigger-or-previous-action>",
"headers": {
"Content-Disposition": "form-data; name=file; filename=<file-name>"
}
}
]
}