How to Automate Gmail to Drive Document Intake?
Description
Move email attachments from Gmail into a selected Google Drive folder without manual work. Useful for teams that receive files from a known sender such as a vendor, a portal, or an internal system and need fast, consistent filing. Less inbox noise and quicker access to documents.
An always on Gmail trigger watches for unread messages from a specific address and downloads every attachment with a clear name prefix. Each file is split into its own item so the flow can handle them one by one without confusion. A switch checks size rules to decide where each file goes and valid files upload to Google Drive with the original file name and content. The Drive node pulls the file name and the file body from the first attachment automatically using safe expressions, so it still works when attachment keys and names change.
Setup uses Gmail and Google Drive accounts in n8n Cloud with OAuth credentials. Choose the Drive folder, confirm the sender filter, and tune the size limits in the Switch node to ignore tiny icons and flag very large files for review. Expect faster filing, fewer mistakes, and a repeatable handoff for invoices, signed forms, reports, and other email based documents.
Tools Required
What this workflow does?
- Gmail trigger watches unread emails from a specific sender and downloads attachments
- Attachments get a clear prefix so files are easy to handle
- Split Out creates one item per attachment for clean, step by step processing
- Switch routes files by size to upload, notify, or ignore branches
- Google Drive uploads files to a chosen folder with the original file name
- Expressions pick the correct attachment key automatically even when names vary
- Polling every minute keeps the Drive folder up to date
What are the benefits?
- Reduce manual work from 30 minutes a day to 2 minutes by auto saving attachments to Drive
- Automate 90 percent of attachment handling from a known sender
- Improve accuracy by 95 percent by removing copy and paste steps
- Cut storage clutter by ignoring tiny icon files and only keeping real documents
- Handle higher volume by processing new emails every minute without extra staff
How to set this up?
- Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
- You'll need accounts with Gmail and Google Drive. See the Tools Required section above for links to create accounts with these services.
- Open the Gmail Trigger node. In the credential field, click Create new credential and follow the on screen steps to connect your Gmail account with OAuth.
- In the Gmail Trigger settings, set the Sender filter to the email address you expect files from, keep Read status as unread, and enable Download attachments with the default attachment prefix.
- Confirm the poll interval is every minute or change it to match your needs.
- Open the Google Drive node. In the credential field, click Create new credential and follow the on screen steps to connect your Google Drive account with OAuth.
- Select My Drive and choose the target folder. Keep the file name and input field expressions so the upload uses the attachment file name and the correct binary field.
- Open the Split Out node and confirm the field is set to $binary so each attachment is processed separately.
- Open the Switch node and adjust the size rules for Large Files and small icons. Pick limits that match your policy, such as ignoring files under a small size and flagging very large files for review.
- If you want alerts for large files, replace the placeholder notification node with your email or chat tool and connect it to the Large Files branch.
- Send a test email from the chosen sender with two attachments, including a small image. Check the workflow execution in n8n to confirm routing and uploads.
- Review the Drive folder to verify file names and contents. If nothing appears, check the Gmail credential, sender filter, and that the email is unread. If names look wrong, confirm the expressions reference the first binary key and file name.
Need help or want to customize this?
Ask in the Free Futurise Community.
Similar Templates
These templates were sourced from publicly available materials across the web, including n8n’s official website, YouTube and public GitHub repositories. We have consolidated and categorized them for easy search and filtering, and supplemented them with links to integrations, step-by-step setup instructions, and personalized support in the Futurise community. Content in this library is provided for education, evaluation and internal use. Users are responsible for checking and complying with the license terms with the author of the templates before commercial use or redistribution.Where an original author was identified, attribution has been provided. Some templates did not include author information. If you know who created this template, please let us know so we can add the appropriate credit and reference link. If you are the author and would like this template removed from the library, email us at info@futurise.com and we will remove it promptly.
