Readable n8n Workflow Export & Multi-Env CI/CD Pipeline

This advanced n8n workflow automates the export of all workflows from a self-hosted n8n instance, ensuring readable file names and proper directory structure for version control and CI/CD pipelines. It processes exported JSON files, renames them for clarity, and duplicates them into environment-specific folders (dev/prod) based on workflow tags like 'Auto deploy to dev'. Ideal for teams managing multiple environments, it eliminates manual export hassles and enables seamless integration with Git and container builds.

Key benefits include improved developer experience through human-readable exports, automated environment separation for safe deployments, and bonus CI/CD assets like a custom Dockerfile and entrypoint script. The Dockerfile packages workflows into n8n containers, while the entrypoint handles imports and triggers a starter workflow. Environment variables such as STARTUP_WORKFLOWS_LOAD_LOCATION and STARTUP_WORKFLOW_ID allow precise control over imports and activations post-deployment.

Use cases span DevOps teams automating n8n updates, agencies delivering client workflows via pipelines, and enterprises enforcing multi-env promotions. Tag production-ready workflows, run the exporter, commit changes, and deploy via CI/CD—no more disabled imports or manual fixes. Compatible only with self-hosted n8n using community nodes; perfect for scalable automation without downtime.