Thank you for your reply @jjurisch! Unfortunately, I have not solved it, yet, but I might have gotten slightly closer. I used the code below. I got the code for "Attachments" by examining the code of another simple flow which saved this attachment into my sharepoint documents folder, so I can be sure that the information under "Attachments" is correct.
My problematic flow, which I hope will attach this saved file to a draft outlook e-mail using an HTTP POST Request, now gives me a different warning than before: "were unable to deserialize".
Can anyone tell me whether this relates to jjurisch comment about decoding the Base64 string? If yes, I suppose I should parse/decode the string value (meaning the strings of "Id" and "ContentType"? or all fields?) into email values?
Kind regards
{
"subject": "attachment ",
"body":{
"contentType":"HTML",
"content":"Dear X, how are you doing? Bye, Y",
"Attachments": [
{
"@odata.type": "#Microsoft.OutlookServices.FileAttachment",
"Id": "AAMkADkwOWU0MG…
"LastModifiedDateTime": "2022-01-27T15:06:43+00:00",
"Name": "test_BB_.xlsx",
"ContentType": "application/vnd.openxmlformats-officedocument.spreadsheetml.sheet",
"Size": 18246,
"IsInline": false,
"ContentId": null,
"ContentBytes": "UEsDBBQABgAIAAAAIQDuoo…
}
]
},
"toRecipients":[
{
"emailAddress":{
"address":"me.me@me.com"}
}
],
"ccRecipients":[
{
"emailAddress":{
"address":"me.me@me.com"}
}
],
}
I alternatively tried to directly attach the email attachments to the HTTP POST Request (I have to use PA in German). No luck though:
The error message body upon examining:
{
"error": {
"code": "BadRequest",
"message": "Unable to read JSON request payload. Please ensure Content-Type header is set and payload is of valid JSON format.",
"innerError": {
"date": "2022-01-27T15:53:51",
"request-id": "ab80e8ef-e4ee-4927-a837-677f510b545c",
"client-request-id": "ab80e8ef-e4ee-4927-a837-677f510b545c"
}
}
}
