Back up the database with Google Drive
Runs on a schedule across Google Drive, Slack and Google Sheets, parses the incoming file into rows, then branches on the check before anything is written. Built for data transforms, around a "Download from Google Drive" step, in 21 documented nodes.
Back up the database with MySQL and Google Drive with instant alerts. An original, ready-to-import n8n workflow built around the 'Backup & Archive' pattern for software development & devops. It runs on a schedule and orchestrates 21 nodes across Google Drive, Slack, Google Sheets. Retry-on-fail is enabled on external calls. Import the JSON, add your credentials, and adapt the parameters. The result is a hands-off process that just works.
Key benefits
- ✓Keeps Google Drive and Slack in step for data transforms, without anyone re-typing a row
- ✓Safe to re-run: records already in Google Drive or Slack are skipped, across all 21 nodes of this data-transforms build
- ✓A failed Google Drive or Slack call is retried rather than dropped, at any of the 21 nodes in this data-transforms build
- ✓Every data-transforms run leaves an audit row behind, alongside Google Drive
- ✓Fans the same result out to Google Sheets in the same run, for data transforms
Use cases
- →Teams keeping Google Drive and Slack aligned by hand for data transforms
- →Data transforms work where "Download from Google Drive" is still a manual step before Google Drive
- →Data transforms work that only reaches Google Drive on a schedule, when someone remembers to start it
Integrations
Workflow preview (21 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (21 nodes)
A look at the node types this workflow uses. No purchase required — full parameters and credentials are yours after you buy.
From download to running in 3 steps
- 1Import. In n8n, open Workflows → menu → “Import from File” and pick the downloaded JSON.
- 2Connect. Add your own credentials on the app nodes - n8n highlights exactly which ones need them.
- 3Activate. Run it once to test, then toggle Active. The automation is live.
What you'll learn
Production levelProduction-grade: idempotency, dead-letter handling, and reconciliation included.
- •Exporting a dataset and serializing it to a file
- •Alarming on an empty backup instead of failing silently
- •Moving data between Google Drive, Google Sheets and MySQL in a single run
Every node carries its own documentation on the canvas, plus notes explaining why the architecture was built this way, a credential setup guide, troubleshooting, and three practice exercises. Sample data comes pinned to the trigger, so you can hit Execute and watch data flow before connecting a single account.
Common questions
What exactly do I get?
The complete, ready-to-import n8n workflow as a JSON file, delivered instantly after payment. Import it into your own n8n (cloud or self-hosted), add your credentials, and it runs.
How do I import it into n8n?
In n8n, open Workflows, click the three-dot menu, choose “Import from File”, and select the downloaded JSON. Then connect your own app credentials on the highlighted nodes.
Do I need anything else for it to work?
You need your own n8n instance and accounts/credentials for the apps this workflow connects to (Google Drive, Slack, Google Sheets, MySQL). No coding is required.
What if it doesn't work for me?
If the file is faulty, won't import, or isn't as described, contact us within 7 days and we'll fix it or refund you - see our refund policy.
Can I modify or resell it?
You can freely adapt and use it in your own or your clients' projects. Reselling or redistributing the template file itself is not permitted.
Related templates
Archive key records: Notion
Helpers on n8n: runs on a schedule across Notion, Google Drive, Telegram, Slack, Google Sheets and MySQL, starting at "Export All Rows (Notion)". 30 documented nodes.
Snapshot the database: Google Sheets, scheduled
Helpers on n8n: runs on a schedule across Google Sheets, Slack, MySQL, Google Drive and Telegram, starting at "Fetch Changes Since Watermark". 21 documented nodes.
Snapshot the database with Google Sheets
Helpers on n8n: runs on a schedule across Google Sheets, MySQL, Microsoft Teams, Slack and Google Drive, starting at "Fetch Changes Since Watermark". 23 documented nodes.
Back up key records: Google Sheets
Backups on n8n: runs on a schedule across Google Sheets, Notion, MySQL, Outlook, Slack and Google Drive, starting at "Fetch Changes Since Watermark". 31 documented nodes.