Scenario backups in a repository — with version history

On a schedule the scenario saves all your scenarios to GitHub: it updates changed ones, adds new ones and removes stale files.

  • Automatic backups of all scenarios on a schedule
  • Version history and rollback to a working state
  • Changed ones updated, new ones added
  • Stale files cleaned up automatically
GitHubn8n
Set it up for yourselfScriptera

How it works

To keep GitHub and in sync, connect them with a ready-made scenario — changes flow automatically.

  1. Starts when: Schedule Trigger
  2. Then: List Files in GitHub Repo
  3. Then: Collect GitHub Filenames
  4. Then: Fetch All n8n Workflows
  5. Then: Filter Changed/New Workflows
  6. Then: Convert Workflow to JSON File
  7. Then: Encode as Base64
  8. Then: Build Filename & Commit Date
  9. Check: File Already Exists in Repo?
  10. If yes: Update Existing File
  11. Then: Find Orphaned Files to Delete
  12. Check: Any Files to Delete?
  13. If yes: Delete Orphaned File
  14. If no: Create New File

You can launch this integration in Scriptera: describe the task in plain words — the scenario is built, launched and monitored for you.

Similar scenarios