Hi Netroy, in this post above I think you give the answer to the problem I’m facing. I would like to ask you if you could change the behavior of the n8n-node as you said there in the last sentence: “If you feel that this behavior is incorrect, then we can add the file-name in the download URL, and then use that file-name for the downloaded file instead.”
I try to download a PDF file from an Airtable attachment field and send it via an SMTP-Node as email attachment. The email arrives with the correct file attached, but that file doesn’t have a .pdf ending. Non-tech-savvy recipients then can’t open it.
I figured it out! The problem was that I’m using another workflow to create that pdf-document in the first place (by merging 2 other pdf files) and then name that new pdf file with a variable filename from another formula field. In that formula I simply added “.pdf” at the end and voila, it works! I just never saw that the file stored in Airtable has no file ending as the Finder on Mac automatically adds .pdf to the filename when downloading it manually from Airtable.