Ops & Monitoring · n8n

Weekly Sheets Backup: timestamped copies of your business-critical spreadsheets, kept tidy

An n8n workflow that exports your most important Google Sheets — the CRM, the orders log, the bookkeeping — as timestamped Excel files into a dated Google Drive folder every Sunday night, keeps the last 12 weeks, and deletes older copies automatically.

difficulty Beginnersetup 15 minresult The 'someone deleted the tab' disaster becomes a 2-minute restore
  1. 1

    List what deserves protection

    A Code node holds the array of spreadsheet IDs and friendly names — CRM, orders, bookkeeping, inventory. Adding a sheet to the backup set is a one-line edit.

  2. 2

    Export every Sunday 23:00

    A Schedule Trigger loops the list through Google's export endpoint (.../export?format=xlsx) via an HTTP Request node using your existing Google credential. Each file downloads as binary, named crm_2026-06-15.xlsx.

  3. 3

    Upload into a dated folder

    A Google Drive node ensures /Backups/2026-06-15/ exists and uploads each file there. One folder per week keeps restores obvious: open the date you want, download, done.

  4. 4

    Prune and confirm

    A Google Drive search lists folders under /Backups older than 12 weeks and deletes them. A final Telegram message — 🗄️ 4 sheets backed up (2.1 MB) · 12 weeks retained — confirms the run. Silence from this workflow is the only alert you need to investigate.

Frequently asked questions

Doesn't Google Sheets have version history already?

It does, and it saves you from most accidents — but it lives inside the same document and the same account. It won't help when the file itself is deleted or the account is compromised, and restoring a single tab's state from six weeks ago via version history is an archaeology project. An exported .xlsx snapshot is a real, independent copy.

Why keep 12 weeks and not everything?

Because backups nobody prunes become a junk drawer nobody trusts. Twelve weekly snapshots cover a quarter — enough to recover from slowly-discovered damage — while staying navigable. Change one number in the Code node if your compliance needs differ.

Can the copies go somewhere other than Drive?

Yes — swap the upload node for Dropbox, S3, or FTP (n8n has nodes for each). Same-cloud backups protect against deletion and mistakes; a different provider also protects against account-level lockout. For business-critical sheets, doing both is cheap.

Related recipes

SSL & Domain Expiry Guard: never lose a weekend to a certificate that expired at 2 AM

An n8n workflow that checks the SSL certificate and domain expiry dates for every domain you own, once a day, and warns you at 30, 14, 7, and 1 day(s) before anything lapses — the boring automation that prevents the most embarrassing outage there is.

Beginner · 15 min setup

Website Down Alert: know your site is broken before your customers tweet about it

An n8n workflow that checks your critical pages every 5 minutes — homepage, checkout, API health endpoint — verifies both status code and expected content, and alerts your Telegram with escalating urgency: one failure logs quietly, two consecutive failures ping you, recovery reports itself.

Beginner · 20 min setup

Brand Mention Tracker: know what the internet said about you today — in one evening digest

An n8n workflow that sweeps Google News RSS and Reddit for your brand name (and common misspellings) every few hours, has Claude judge sentiment and importance, and sends one evening Telegram digest — with an instant bypass alert if something negative starts moving.

Beginner · 25 min setup
About this recipe. Recipes on FlowRecipesHub are written for business owners, not developers, and are tested before publishing — how recipes get made. Some ingredient links are affiliate links that cost you nothing — full disclosure.