It looks like the issue is caused by the way you're constructing your attachment objects. Below is how I would likely build the entire flow, including deleting the images after the email has been sent.
For this example, I'm using the following folder to hold my images.
Below is the full flow. I'll go into each of the actions.
Recurrence is set to run daily at 11PM.
Get items (properties only) retrieves the images from the folder. Note that I've also added the following filter so it only returns files (NOT folders). This means we don't have to add a Condition to check if it's a folder or file as only files will be returned.
FSObjType eq 0
Initialize variable creates an array variable called attachments which will eventually contain all our images.
Next, I have a Condition to check that at least one image was returned. If no images returned (no images in the folder) then we don't progress any further (No branch). If at least one image returned, then we go into the Yes branch. The expression in the condition is:
length(outputs('Get_files_(properties_only)')?['body/value'])
Apply to each Attachment will iterate over each of the images returned.
Get file content retrieves the content of the image.
Append to array variable builds up our attachment object, including the Name and ContentBytes. Name uses File name with extension from Get files, and ContentBytes uses Body from Get file content. It then appends the object to our attachments array.
{
"Name": @{items('Apply_to_each_Attachment')?['{FilenameWithExtension}']},
"ContentBytes": @{body('Get_file_content')}
}
After the Apply to each Attachment, we use Send an email adding the attachments array.
We then have Apply to each Image to Delete that will iterate over each of the images returned and delete each one, so our folder is ready for the next lot of images.
In this example, the email received would look like the following:
----------------------------------------------------------------------
If I've answered your question, please mark the post as Solved.
If you like my response, please consider giving it a Thumbs Up.
