To back up Google Sheets to Google Drive with n8n, schedule an export, retrieve the spreadsheet or its rows, convert the result to CSV or XLSX, upload it to a dated Drive folder, verify the uploaded file, and alert someone when the backup fails. A good backup workflow also has a retention policy and a restore test.
Before you build: define what “backup” means
There are two common goals:
Data snapshot: save values from one worksheet as CSV or XLSX. This is easy to inspect and restore into many tools.
Native spreadsheet copy: duplicate the Google Sheets file, preserving more spreadsheet behavior such as multiple tabs and formatting.
A row export is not a complete native copy. Formulas may become values, formatting may be lost, and linked objects or permissions are not reproduced. Choose the method that matches your recovery requirement.
Option A: export worksheet data to CSV
1. Create the Schedule Trigger
Run daily, weekly, or at the end of a business process. Set the workflow timezone deliberately. For critical data, schedule the backup after source updates normally finish and before downstream cleanup begins.
2. Retrieve rows from Google Sheets
Use the Google Sheets node to read the target document and worksheet. Decide whether the first row contains headers and whether blank rows should be included. If the sheet can grow large, test memory use and split the export when necessary.
3. Add backup metadata
Create fields for spreadsheet ID, worksheet name, backup timestamp, row count, workflow execution ID, and a content version or checksum when available. This metadata makes support and restore work much easier.
4. Convert the rows to a file
Use n8n’s file-conversion capability to create CSV or XLSX binary data. A clear file name might be:
sales-pipeline__leads__2026-08-19T020000Z.csv
Use UTC or include the timezone in the naming standard. Avoid slashes and characters that create inconsistent paths.
5. Upload to Google Drive
Use the Google Drive node to upload the binary file into a dedicated backup folder. Organize files by source and date, for example:
Automated Backups / Sales Pipeline / 2026 / 08 /
Keep backup storage separate from the working spreadsheet folder so accidental cleanup rules do not remove both.
6. Verify the upload
Do not treat a successful upload request as the entire verification. Record the returned Drive file ID, size, name, and timestamp. Confirm the file is non-empty and the exported row count matches the source count expected for that run.
Option B: make a native Google Drive copy
If preserving multiple worksheets, formulas, and formatting matters, use the Google Drive API’s copy operation through a supported node operation or an authenticated HTTP Request. Copy the source file into the backup folder with a timestamped name.
Native copies may also reproduce sharing behavior depending on API settings and Drive context. Review permissions and test with the exact type of Shared Drive or My Drive location you use.
Add a retention policy
Unlimited backups become a storage and privacy problem. A practical policy might keep:
daily backups for 14 days;
weekly backups for 8 weeks;
monthly backups for 12 months.
Implement deletion only after you can positively identify files created by the backup workflow. Filter by dedicated folder, naming prefix, age, and metadata. Send the deletion candidate list to a log or approval step before enabling automatic cleanup.
Recommended node sequence
Schedule Trigger
Set: source configuration and timestamp
Google Sheets: read rows
Code or aggregate step: count and normalize rows
Convert to File: CSV or XLSX
Google Drive: upload
IF: validate file ID, size, and row count
Log success to a backup register
Error branch: notify the owner with a safe summary
Credential and security guidance
Give the Google credential access only to the documents and folders it needs.
Use a dedicated backup folder with restricted membership.
Do not include secrets or sensitive personal data in notifications.
Review OAuth consent and token access when staff roles change.
Encrypt and protect the n8n credential store and encryption key.
Test the restore—not just the backup
Once per month or quarter, select a recent backup and restore it into a temporary spreadsheet. Check headers, row count, data types, dates, formulas if expected, and important sample records. Record the test result and how long recovery took.
If nobody has opened a backup, you have an automated file archive—not a proven recovery process.
Frequently asked questions
Can n8n back up multiple Google Sheets?
Yes. Store spreadsheet configurations in a list, database, or control sheet and loop through them. Limit concurrency to avoid Google API rate limits.
Should I use CSV or XLSX?
CSV is simple and portable for a single table. XLSX supports multiple sheets and richer data presentation. A native Drive copy preserves the most Google Sheets behavior.
What if the sheet is empty?
Decide whether an empty export is valid. For business-critical sheets, treat an unexpected zero-row result as a warning and keep the previous backup.
N8nPort customers can start with a curated Google Sheets automation, install it into a managed workspace, connect their own Google credentials, and test the full backup-and-restore path before activation.