Archive key records: MySQL
Runs on a schedule across MySQL, Google Drive and Slack, parses the incoming file into rows, then branches on the check before anything is written. Built for backups, around a "Download from Google Drive" step, in 14 documented nodes.
Archive key records 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 14 nodes across MySQL, Google Drive, Slack. Retry-on-fail is enabled on external calls. Import the JSON, add your credentials, and adapt the parameters. Nothing slips through the cracks.
Key benefits
- ✓Keeps MySQL and Google Drive in step for backups, without anyone re-typing a row
- ✓A failed MySQL or Google Drive call is retried rather than dropped, at any of the 14 nodes in this backups build
- ✓Fans the same result out to Slack in the same run, for backups
- ✓Pinned sample data ships with it — run all 14 nodes for backups before wiring MySQL
- ✓14 nodes, each with a doc card explaining what it does for backups
Use cases
- →Teams keeping MySQL and Google Drive aligned by hand for backups
- →Backups work where "Download from Google Drive" is still a manual step before MySQL
- →Backups work that only reaches MySQL on a schedule, when someone remembers to start it
Integrations
Workflow preview (14 nodes)
The template's actual node layout and connections. Node parameters and credential slots unlock with the download.
What's inside (14 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
Core levelA compact production shape: validation and error handling without extra machinery.
- •Exporting a dataset and serializing it to a file
- •Alarming on an empty backup instead of failing silently
- •Moving data between Google Drive, MySQL and Slack 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 (MySQL, Google Drive, Slack, Discord). 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 on a schedule
Backups on n8n: runs on a schedule across Google Sheets, Google Drive, Slack, Airtable and Discord, starting at "Download from Google Drive". Parses the incoming file into rows. 23 documented nodes.
Archive key records with Notion
Backups on n8n: runs on a schedule across Notion, Google Drive, MySQL, Slack and Microsoft Teams, starting at "Download from Google Drive". Parses the incoming file into rows. 31 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.
Archive key records: Notion, scheduled
Backups on n8n: runs on a schedule across Notion, Google Sheets, Discord, Slack and Google Drive, starting at "Fetch Changes Since Watermark". 33 documented nodes.