Make.com Dropping Large Email Attachments? Here's How I Fixed It.
Setting up a new automation in Make.com usually feels like magic. You connect a few blocks, map some fields, and boom – things just work . This time, though, I hit a wall with something that should have been simple: taking email attachments and dropping them into Google Drive. The Ghosting Problem: Attachments Vanish My goal was straightforward: whenever I received an email with an attachment in…
Make.com users were discovering issues with large email attachments not successfully uploading to Google Drive. The problem only affected files larger than about 20-25MB. Despite the automation showing success, the attachments weren't appearing in the designated Google Drive folder. The author of the account tried several troubleshooting steps including examining logs, checking folder permissions, researching size limits, reconfiguring modules, and testing different email sources.
None of these worked to resolve the issue. The key insight came when looking closely at the output bundle from Make.com's Gmail - Get an Attachment module. This module provides a webContentLink, a temporary URL that can be used to download the attachment directly. The author realized that perhaps the direct data transfer between modules wasn't robust enough for larger files.
After inserting an HTTP - Get a File module between the Gmail and Google Drive modules, the large attachments were successfully uploaded to Google Drive. The HTTP module explicitly downloaded the file using the webContentLink, bypassing any potential internal handling limitations in Make.com for massive files. This change allowed large files to be reliably uploaded, proving that explicit file downloading sometimes provides a more robust solution than direct module-to-module data transfer for very large files.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
