Backups of your scenarios — with a change history

The scenario regularly saves all your scenarios to репозиторий, updates only the changed ones and sends a change summary to Google Chat.

  • All scenarios on a schedule
  • Only changed ones updated
  • A version history in репозиторий
  • A change summary in Google Chat
GitHubn8n
Set it up for yourselfScriptera

How it works

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

  1. Starts when: Schedule Trigger
  2. Then: Configuration
  3. Check: Assert GitHub config
  4. If yes: Get all workflows
  5. Then: Encode N8N workflows
  6. Check: Merge
  7. Check: Loop Over Items
  8. Check: Is Telegram configured?
  9. If yes: Build summary arrays
  10. Check: Anything changed?
  11. If yes: Render summary
  12. Then: Send a message
  13. Then: Decide changes
  14. Check: Router
  15. If yes: Delete old file
  16. Check: Merge after delete (rename)
  17. Check: Merge after create (rename)
  18. Then: Create new file (rename)
  19. If no: Update file content and commit
  20. Check: Merge after update
  21. If no: Create new file
  22. Check: Merge after create
  23. If no: Stop and Error
  24. If yes: List files
  25. Then: Get files
  26. Then: Extract workflow parameters
  27. If no: Stop on empty config

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

Similar scenarios