Templates / Back up workflows daily to GitHub with incremental updates

Back up workflows daily to GitHub with incremental updates

Ready for 3.0

by Corenexis · 20 views · created 2026-07-04 · DevOps

Ready for 3.0. This template uses no nodes that n8n 3.0 removes. No removed nodes, versions or helpers found. Static check, last run 2026-10-19.

What this workflow does

This workflow has 14 nodes and runs on a schedule (every day at 23:00). Along the way it connects GitHub. It also calls api.github.com over HTTP.

How it runs

Trigger: On a schedule (every day at 23:00).

  1. Get many workflows (n8n): uses n8n
  2. Loop Over Items (Loop Over Items (Split in Batches)): loops over the items in batches
  3. Get a file (GitHub): get (file)
  4. If: checks a condition and branches into true / false
  5. Get Last Update Date (HTTP Request): calls api.github.com
  6. Get a workflow (n8n): get
  7. filter_date (If): checks a condition and branches into true / false
  8. Create a file (GitHub): work with file
  9. Download workflow (n8n): get
  10. Wait: waits 10 seconds

…plus 3 more steps. See the full node list below.

Services it uses

GitHub

HTTP calls to: api.github.com

Before you upgrade to n8n 3.0

Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.

Nodes used (7)

From the author

Quick overview This workflow runs nightly to back up all workflows from your n8n instance to a GitHub repository, creating a new JSON file for new workflows and only updating existing files when the workflow has changed to avoid unnecessary commits. How it…

Excerpt from Corenexis's description on n8n.io.

View the original on n8n.io → Check your own copy

Get the weekly “what broke” email

New templates, newly broken ones, and n8n release changes. One short email a week.

Form not loading? Subscribe here.