Backup n8n Workflows to Google Drive (JSON) via Public API
Backup n8n Workflows to Google Drive (JSON) via Public API
Regular price
£59.99
Regular price
£59.99
Sale price
Unit price
/
per
⬇
Instant Digital Download
∞
Unlimited Downloads
★
Lifetime Access in Your Account
Couldn't load pickup availability
🔥
128+ Sold
Popular with n8n builders
⚡
23 people viewing
High interest right now
✅
9 added today
Fast-moving digital product
Backup n8n Workflows to Google Drive (JSON) via Public API
Regular price
£59.99
Regular price
£59.99
Sale price
Unit price
/
per
Back up your n8n workflows to Google Drive as JSON—on demand
This n8n automation workflow fetches all workflows from your n8n instance via the n8n Public API, converts each one into a pretty JSON file, and uploads the backups to a specified Google Drive folder—so you can reliably preserve and restore your automation logic.
What this workflow does
- Runs manually when you click “Test workflow” in n8n.
- Calls the n8n Public API using an API key to retrieve all workflows (via GET /workflows) from your configured n8n base URL (e.g., http://localhost:5678/api/v1).
- Splits the returned workflow list so each workflow is processed individually.
- Converts each workflow object into a prettified JSON file with a safe filename.
- Uploads every JSON backup file to the target Google Drive folder you specify.
Use cases
- SaaS operators who need periodic or ad-hoc backups of n8n automations for change management.
- Automation engineers who want a quick export trail before refactoring workflows.
- Environment management (dev/staging/prod) where you want consistent JSON snapshots stored in Google Drive.
- Disaster recovery planning by keeping readable workflow JSON backups outside the n8n instance.
Technical details
- Nodes/approach: set, code, split out, sticky note, HTTP Request, Google Drive
-
Integrations:
- n8n Public API (API key + base URL; requests GET /workflows)
- Google Drive via OAuth2 credential
- Setup requirements: create an n8n Public API key; configure the n8n instance base URL; add Google Drive OAuth2 credentials; set the target Google Drive folder ID/URL in the upload step.
