A version history of your scenarios, saved on change

On a schedule the scenario checks what changed in your scenarios and connections, and only on a change exports a fresh copy to a repository with history.

  • A version history for rollbacks
  • A copy saved only when something changes
  • Change detection on its own
  • Always something to roll back to
Set it upScriptera

How it works

To move data from S3 to automatically, use a ready-made scenario — no manual exports.

  1. Starts when: Schedule Trigger
  2. Then: Set Workflow Path
  3. Then: Get Old Workflow Hash
  4. Then: Execute Workflow Backup
  5. Then: Get New Workflow Hash
  6. Check: If Workflow Updated
  7. If yes: Read Workflow Data
  8. Then: Extract Workflow Data
  9. Then: GitHub Workflow Backup
  10. Then: Set Credential Path
  11. Then: Get Old Credential Hash
  12. Then: Execute Credential Backup
  13. Then: Get New Credential Hash
  14. Check: If Credential Updated
  15. If yes: Read Credential Data
  16. Then: Extract Credential Data
  17. Then: GitHub Credential Backup
  18. Then: Read File
  19. Then: Extract Data
  20. Then: Hash Data
  21. Starts when: Hash Maker

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

Similar scenarios