Scenario backups to a repo via pull request

The scenario finds new and changed scenarios, commits them to репозиторий as a pull request, and notifies the team in vk.

  • New and changed scenarios auto-committed
  • A separate pull request per change
  • A notification to your chat
  • Roll back and compare any time
n8nGitHub
Set it up for yourselfScriptera

How it works

To get vk notifications in GitHub, you don't need a developer: a ready-made scenario watches events and sends messages for you.

  1. Starts when: Click me to trigger
  2. Then: Define Local Variables
  3. Then: n8n
  4. Check: Find new workflows
  5. Check: Wait until branch created1
  6. Check: Filter empty data
  7. Then: Create new commit to add new workflow
  8. Check: Wait for GitHub create/edit file finished
  9. Then: Create new PR via GitHub API
  10. Then: Slack
  11. Check: Wait for finished
  12. Check: If there are any changes in workflows
  13. If yes: Get latest commit SHA on main via GitHub API
  14. Then: Create new branch via GitHub API
  15. Check: Wait until branch created
  16. Check: Filter empty data1
  17. Then: Create new commit to update changed workflow
  18. Check: Find updated workflows
  19. Then: Get all workflows on GitHub
  20. Then: Get content for each workflow
  21. Then: Base64decode workflow content

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

Similar scenarios