✨ $500 AI Visibility Audit — live at Spurlock Studios. Book the audit

Operations & Systems

Auto-Download Attachments from Gmail -> GDrive

This n8n workflow monitors Gmail for new emails, downloads attachments, and uses a Switch node to filter them by size. Medium-sized attachments are then automatically uploaded to Google Drive. Other sizes are routed to placeholder actions for further processing or ignored.

Built · ~6 hours saved per week

Workflow Overview: Gmail Attachment Archiver This workflow automates the process of managing and archiving attachments from incoming emails. It actively monitors a Gmail account for new, unread messages, extracts any attachments, filters them based on their file size, and then uploads the relevant files to a designated folder in Google Drive. Technologies Used - Gmail: Serves as the trigger and source of the email attachments. - Google Drive: Acts as the destination cloud storage for the archived files. - n8n: The core automation platform that connects the services and executes the logic. Automation Value This workflow provides a "set-it-and-forget-it" solution for handling email attachments, delivering significant value by: - Saving Time: Eliminates the manual, repetitive task of checking emails, downloading attachments, and re-uploading them to cloud storage. - Improving Organization: Ensures that important files sent via email are consistently backed up and stored in a centralized, accessible location. - Intelligent Filtering: Automatically sorts attachments by size to prevent clutter. It ignores small, insignificant files (like email signature icons) and can be configured to flag unusually large files for review, ensuring storage is used efficiently. --- Node-by-Node Analysis H3: Gmail Trigger - Purpose: To start the workflow whenever a new, unread email arrives. - Execution: The node is configured to poll a specific Gmail account every minute. Its most critical setting is downloadAttachments: true, which fetches the actual file data from the email and makes it available to the rest of the workflow as binary data. H3: Split Out - Purpose: To process each email attachment individually. - Execution: A single email can contain multiple attachments. The Gmail Trigger node places all these attachments within one workflow execution. This Split Out node takes that single execution and creates separate, individual items for each attachment. This is essential for handling each file one by one in the subsequent steps. H3: Switch - Purpose: To route attachments based on their file size. This is the "brain" of the workflow.

Tags: Google

Integrations: Email, Google Drive

Related automations

Back to the Automation Library