Scheduled Google Sheets data backup to Google Drive

Needs changes

by David Olusola ✓ · 287 views · created 2025-07-26 · File Management

Needs changes. This template uses 1 thing(s) that n8n 3.0 removes: Cron. 1 breaking item(s) found. Static check, last run 2026-10-19.

What this workflow does

This workflow has 3 nodes and runs on a schedule (legacy Cron node). Along the way it connects Google Sheets and Google Drive.

How it runs

Trigger: On a schedule (legacy Cron node).

Read Google Sheet Data (Google Sheets): get many
Upload Backup to Google Drive (Google Drive): uses Google Drive

Services it uses

Google Sheets Google Drive

Before you upgrade to n8n 3.0

1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:

Cron in Daily Backup Schedule (2 AM): replace with Schedule Trigger.

Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).

Removed in 3.0	Replace with
Cron Daily Backup Schedule (2 AM)	Schedule Trigger

Nodes used (3)

Cronn8n-nodes-base.cron
Google Sheetsn8n-nodes-base.googleSheets
Google Driven8n-nodes-base.googleDrive

From the author

Overview This workflow regularly backs up a Google Sheet by exporting its data and saving it as a new file (CSV or XLSX) in a specified folder within your Google Drive. This ensures data redundancy and historical versions. Use Case: Critical business data…
Excerpt from David Olusola's description on n8n.io.

View the original on n8n.io → Check your own copy

Scheduled Google Sheets data backup to Google Drive

What this workflow does

How it runs

Services it uses

Before you upgrade to n8n 3.0

Nodes used (3)

From the author

Get the weekly “what broke” email