GitHub backups that protect your latest changes
You finally have a workflow running in n8n, then something changes and the “latest” version is… somewhere. A browser export on one laptop, a JSON file in Drive, and a vague memory of “I think I changed that last week.” This is where GitHub backup automation stops being a nice-to-have.
Marketing ops teams feel it when automations power launches. Agency owners feel it when client setups evolve fast. And internal ops leads hate it because one accidental overwrite can cost an afternoon of rework.
This workflow backs up your n8n workflows to GitHub every night, then posts a message to your team chat so changes don’t quietly slip by. You’ll see what’s happening, keep history, and roll back without drama.
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: GitHub backups that protect your latest changes
flowchart LR
subgraph sg0["Flow 1"]
direction LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/github.dark.svg' width='40' height='40' /></div><br/>GitHub Edit"]
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/github.dark.svg' width='40' height='40' /></div><br/>Get Files"]
n2@{ icon: "mdi:code-braces", form: "rounded", label: "Transform", pos: "b", h: 48 }
n3["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/github.dark.svg' width='40' height='40' /></div><br/>Create file"]
n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/merge.svg' width='40' height='40' /></div><br/>Merge"]
n5["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Get workflows"]
n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Get workflow data"]
n7["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>Download Raw Content"]
n8@{ icon: "mdi:code-braces", form: "rounded", label: "transform", pos: "b", h: 48 }
n9@{ icon: "mdi:cog", form: "rounded", label: "Daily at 23:59", pos: "b", h: 48 }
n10["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/merge.svg' width='40' height='40' /></div><br/>Merge1"]
n4 --> n3
n10 --> n0
n1 --> n2
n2 --> n7
n8 --> n6
n5 --> n8
n9 --> n5
n6 --> n4
n6 --> n10
n7 --> n4
n7 --> n10
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n5,n6,n7 api
class n2,n8 code
classDef customIcon fill:none,stroke:none
class n0,n1,n3,n4,n5,n6,n7,n10 customIcon
The Problem: Your “Latest” Automation Isn’t Really Saved
n8n makes it easy to build automations fast, which is great right up until you need a clean copy of what’s currently running. Exporting workflows manually sounds simple, but in real life it’s inconsistent. People forget. Files get renamed. A “final_v3” export shows up after “final_v4.” Then a node breaks, you need to roll back, and you’re stuck guessing which file actually matches production. The time loss is annoying. The bigger issue is confidence: you stop changing things because you’re not sure you can undo them.
The friction compounds. Here’s where it usually breaks down.
- Manual exports happen only after something goes wrong, so you’re always backing up too late.
- Teams store exports in different places, which means nobody trusts the “official” copy.
- When a workflow changes, there’s no simple diff, so reviews turn into screenshots and guesswork.
- Without version history, rollback becomes a rebuild, and that can easily eat half a day.
The Solution: Nightly n8n Workflow Backups to GitHub (With Alerts)
This automation runs on a schedule (every night at 23:59) and automatically pulls your n8n workflows through an HTTP request to your n8n instance. From there, it cleans and structures the data using a Function step, then loops through items in batches so multiple workflows can be processed reliably. Each workflow export is written into your GitHub repo at the file path you define, using your GitHub username and repo name. If something changed since the last run, GitHub captures that change as a commit you can review, diff, and roll back. Finally, the workflow posts an update to your team chat, so people actually notice that automation logic evolved.
The workflow starts with a Cron trigger at night. It then queries your n8n instance over localhost with Basic Auth, merges and filters the results, and pushes updated files to GitHub. Once the backup completes, Mattermost or Twake can notify the team so changes don’t hide in the background.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you maintain 12 active n8n workflows. Manually exporting, naming files, and uploading them to a shared folder takes maybe 5 minutes per workflow, so about an hour each time you “do backups,” and most people only remember weekly. With this automation, it’s basically 0 minutes of effort: the Cron runs at 23:59, the backup processes while you sleep, and your team gets a Mattermost/Twake message when it’s done. You go from “I hope we have a copy” to “open GitHub and revert.”
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- GitHub to store versioned workflow backups
- Mattermost or Twake to notify your team about changes
- n8n Basic Auth credentials (create in n8n Credentials)
Skill level: Intermediate. You’ll configure credentials, repo paths, and one internal HTTP request safely.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
Nightly schedule trigger. A Cron node kicks this off every night at 23:59, so backups happen even when everyone forgets.
Secure export from your n8n instance. HTTP Request nodes call your n8n instance on localhost:5678 and authenticate using Basic Auth credentials you create with your n8n username and password.
Cleanup, filtering, and batching. A Function step shapes the export into consistent files, then Loop Over Items (Split in Batches) processes workflows in manageable chunks. The If and Merge nodes help control what gets committed and when, so the workflow doesn’t spam commits.
Commit to GitHub and notify the team. GitHub nodes write each workflow to the repo and file path you specify. Once it finishes, Mattermost or Twake posts an update, which means changes are visible without someone chasing an “FYI” email.
You can easily modify the schedule time to match your release cadence, or swap the notification channel based on what your team checks. See the full implementation guide below for customization options.
Common Gotchas
- GitHub credentials can expire or need specific permissions. If things break, check the token scopes and the repo access settings first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Those HTTP Request calls hit an internal n8n API on localhost, so Basic Auth and your n8n base URL must match your actual instance. If you changed ports or disabled basic auth, the export will fail fast.
Frequently Asked Questions
About 30 minutes if you already have your repo and n8n credentials ready.
No. You’ll mostly paste credentials and choose your repo name and file path.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in GitHub costs (often free for basic repos) and your hosting costs if you self-host.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, but GitHub is the point if you want diffs and rollback. You can swap the GitHub write/commit portion for Google Drive upload nodes, or run both by keeping GitHub as the “source of truth” and adding a Drive copy for non-technical stakeholders. Common tweaks include changing the Cron time, narrowing which workflows get exported, and sending notifications to Mattermost vs Twake.
Usually it’s an expired token or missing repo permissions. Update the GitHub credential in n8n, then double-check the repo name and file path you configured because a tiny typo can look like an auth issue. If the HTTP export is failing first, confirm your localhost URL, port, and Basic Auth credentials match your n8n instance.
Plenty for most small teams: dozens to a few hundred workflows is normal, as long as your n8n instance and repo aren’t overloaded.
For this use case, yes, most of the time. Zapier and Make aren’t built around calling an internal n8n API on localhost, batching exports, and committing files with the same level of control, so you end up with awkward workarounds. n8n also gives you branching, Merge/If logic, and self-hosting without pricing surprises when executions climb. If you only want a lightweight “send me a message when something changes” automation, a simpler tool might be enough. Talk to an automation expert if you want a quick sanity check.
Once this is running, your backups are just there, every morning. GitHub keeps the history. Your team keeps moving.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
