Issue With Downloading Outlook Attachments

Questions
,
1

Describe the problem/error/question

Hi all. I am trying to use n8n to retrieve an email with attachments (mainly pdfs) and then create a new draft and attach these pdfs to this new draft and send it. This is all done using MS Outlook. However, whenever I try and re-attach the attachments to the draft email, I get an error saying that the n8n node was unable to deserialize the attachment. This is happening to me for a variety of emails and a variety of attachments. I am wondering if anyone out there would be able to help me fix this issue! Thank you!

What is the error message (if any)?

“were unable to deserialize”

Please share your workflow

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
4

Hi @adamjabarry, thanks for posting. This is a known issue we’re working on fixing. I’ll also report your case internally as well. :slight_smile:

5

Hi Aya,
I hope you are doing well. Similar to my other post, I just want to check if there has been any update on this bug?
Best,
Adam

6

Hi @adamjabarry, for this one no updates so far :frowning: but will keep you posted if there are any updates!

7

Hi Aya, pretty much its a major setback for msft outlook users making us look for another solution or switch to google. Appreciate your team looking into this as this has been raised across multiple threads.

8

@Crazydarkman13 have you found any alternatives?

9

mmm Aya dgaf

10

Hello! Anny updates on this ?

11

any updates?>

12

We still don’t have any ETA for the fix sadly, but will keep you posted!