Quick question regarding binary data and the Gmail node. I have a workflow that downloads a PDF from Google Drive, but the Gmail node isn’t attaching it correctly to the outgoing email.
I can see the binary object in the output of the G-Drive node, but I think I’m misconfiguring the ‘Property Name’ in the Gmail attachment field.
Any pointers on how to map this correctly? Screenshot below
@abdouli I think the issue is likely the binary data flow. In n8n, you usually have to use the binary file in the very next node.
Move the download step to right before the Gmail node. Since you can’t reference binary data globally as easily as other variables, keeping the download and the send nodes back-to-back should fix the attachment issue. Give it a try and let me know.
Hope this helps!
That worked perfectly, thanks! Now I’m just looking to optimize the flow. Since I’m sending the same PDF to everyone, I want to avoid re processing/uploading it for every iteration.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
