You can use an HTTP action with the addAttachment request. You have to use a multipart request, which means you don't put the request parameters in the query string of the http request. You construct a Body with the multipart form syntax. Here's an example Body:
{
"$content-type": "multipart/form-data",
"$multipart": [
{
"headers": {
"Content-Disposition": "form-data; name=\"attachment\"; filename=\"@{outputs('Parse_job_result')['body']['resultInfo']['resultFiles'][0]['name']}\""
},
"body": "@{body('HTTP_get_file')['$content']}"
},
{
"headers": {
"Content-Disposition": "form-data; name=\"f\""
},
"body": "json"
},
{
"headers": {
"Content-Disposition": "form-data; name=\"token\""
},
"body": "@{body('Parse_get_token')?['token']}"
}
]
}
There 3 pieces of dynamic content:
Filename: in the case of a S123 feature report, get this from the job result info
Body: use the output of a http get request. In the case of S123 feature reports, use the url parameter returned by the job (if you leave out the uploadInfo parameter the report doesn't get created as a content item but you get a url directly to the Amazon S3 file)
Token: token obtained from generateToken with built-in user credentials
Here are some articles I used:
https://ashiqf.com/2021/07/25/how-to-use-form-data-and-form-urlencoded-content-type-in-power-automat...
https://willpage.dev/2019/12/20/using-the-http-action-to-post-multipart-form-data-in-power-automate-...
