Accepted Solutions
@gbuhreand @SvenG Rest assured there is a way of doing this.
If you want to post multipart form data with binary content via the HTTP connector you must format the body of the request in a certain way.
What they don't tell you (except in an obscure section of the Azure Logic Apps documentation) is that the HTTP action actually deserialises JSON input and converts it to a multipart string value.
Leave the Headers parameter blank. In this example the API documentation says this:
POST /api/gateway.php/sample/v1/employees/1/files/ HTTP/1.0
Host: api.bamboohr.com
Content-Type: multipart/form-data; boundary=----BambooHR-MultiPart-Mime-Boundary----
Content-Length: 520
------BambooHR-MultiPart-Mime-Boundary----
Content-Disposition: form-data; name="category"
112
------BambooHR-MultiPart-Mime-Boundary----
Content-Disposition: form-data; name="fileName"
readme.txt
------BambooHR-MultiPart-Mime-Boundary----
Content-Disposition: form-data; name="share"
yes
------BambooHR-MultiPart-Mime-Boundary----
Content-Disposition: form-data; name="file"; filename="readme.txt"
Content-Type: text/plain
This is a sample text file.
------BambooHR-MultiPart-Mime-Boundary------But I want to post a binary file instead of "This is a sample text file", so while the plain text above works as the body of the HTTP action when the file content is only text, for binary to work I make the HTTP body like this.
{
"$content-type": "multipart/form-data",
"$multipart": [
{
"body": "18",
"headers": {
"Content-Disposition": "form-data; name=\"category\""
}
},
{
"body": "@{outputs('Convert_file')['headers']['x-ms-file-name']}",
"headers": {
"Content-Disposition": "form-data; name=\"fileName\""
}
},
{
"body": "yes",
"headers": {
"Content-Disposition": "form-data; name=\"share\""
}
},
{
"body": {
"$content": "@{body('Convert_file')}",
"$content-type": "application/pdf"
},
"headers": {
"Content-Disposition": "form-data; name=\"file\"; filename=\"@{outputs('Convert_file')['headers']['x-ms-file-name']}\""
}
}
]
}In my example the dynamic content is all from a OneDrive PDF file conversion process, but you can adjust your Flow to suit your needs
@gbuhre wrote:I have updated this request with screen shots
Sorry. with the URLs blacked out, without expanding the steps there isn't much we can help with, as we have no idea which parameters you're parsing in and/or which fields you're trying to access. Expanding the steps and only blacking out what you absolutely must is preferred. Example:
My guess is that the URI you're parsing in, is likely in the incorrect format. A simple way to check if your formatting is correct is copying the URI path from your Flow's run error message, and pasting it into your browser. If it runs and returns the data as expected, your path is okay... my guess is that it won't.
A 400 error is almost always a path or API issue, which means that other than the path, you may be utilizing a POST request when the API is expecting a GET request, or that you may be referencing the wrong part of the API. Again, I am unsure without seeing the expanded steps.
If this reply has answered your question or solved your issue, please mark this question as answered. Answered questions helps users in the future who may have the same issue or question quickly find a resolution via search. If you liked my response, please consider giving it a thumbs up. THANKS!
Here's the Post request without the URL's balcked out. All I'm trying to do is a send a PDF document to my CRM tool.
I got it to work but now I'm having issues view the PDF file. I get an error when I try and open up the PDF about a decoding issue.
I'm taking a PDF file from sharepoint and trying to save it to ConnectWise our CRM tool. When I try and open the file from the CRM tool it says the files is damaged and could not be repaird. I get a 201 when I submit. Let me know if you need any other screen shots.
So little more testing and it's defiantly something with how flow is processing the attachment. If I send the same attachment via Postman it works great. If I take that same file and code and try using flow it says successful but can never open up the file. The two screen shots are from the same file but the encoding is difference one is from flow one is from Postman.
@gbuhreand @SvenG Rest assured there is a way of doing this.
If you want to post multipart form data with binary content via the HTTP connector you must format the body of the request in a certain way.
What they don't tell you (except in an obscure section of the Azure Logic Apps documentation) is that the HTTP action actually deserialises JSON input and converts it to a multipart string value.
Leave the Headers parameter blank. In this example the API documentation says this:
POST /api/gateway.php/sample/v1/employees/1/files/ HTTP/1.0
Host: api.bamboohr.com
Content-Type: multipart/form-data; boundary=----BambooHR-MultiPart-Mime-Boundary----
Content-Length: 520
------BambooHR-MultiPart-Mime-Boundary----
Content-Disposition: form-data; name="category"
112
------BambooHR-MultiPart-Mime-Boundary----
Content-Disposition: form-data; name="fileName"
readme.txt
------BambooHR-MultiPart-Mime-Boundary----
Content-Disposition: form-data; name="share"
yes
------BambooHR-MultiPart-Mime-Boundary----
Content-Disposition: form-data; name="file"; filename="readme.txt"
Content-Type: text/plain
This is a sample text file.
------BambooHR-MultiPart-Mime-Boundary------But I want to post a binary file instead of "This is a sample text file", so while the plain text above works as the body of the HTTP action when the file content is only text, for binary to work I make the HTTP body like this.
{
"$content-type": "multipart/form-data",
"$multipart": [
{
"body": "18",
"headers": {
"Content-Disposition": "form-data; name=\"category\""
}
},
{
"body": "@{outputs('Convert_file')['headers']['x-ms-file-name']}",
"headers": {
"Content-Disposition": "form-data; name=\"fileName\""
}
},
{
"body": "yes",
"headers": {
"Content-Disposition": "form-data; name=\"share\""
}
},
{
"body": {
"$content": "@{body('Convert_file')}",
"$content-type": "application/pdf"
},
"headers": {
"Content-Disposition": "form-data; name=\"file\"; filename=\"@{outputs('Convert_file')['headers']['x-ms-file-name']}\""
}
}
]
}In my example the dynamic content is all from a OneDrive PDF file conversion process, but you can adjust your Flow to suit your needs
Helpful resources
Power Automate News & Announcements
Keep up to date with current events and community announcements in the Power Automate community.
