Being able to save configuration to version control and have reproducible builds is important for modern workflows (CI/CD systems, etc). For example, I develop some n8n workflows on my local environment. I should have an option for n8n to automatically save the json configs to file so that they can be checked into version control. And when I promote to staging/production, I should be able to manually or programmatically run a migration task that reads in these files and sets up the exact state as development (with the ability to read in environment specific values). This would allow you to roll back to specific versions of a n8n workflow. For example, I might be running the latest iteration of my n8n workflows on staging for testing purposes while a version behind on production. Having this type of feature is essential for modern application development and deployment and would also help differentiate n8n vs some of the other options.