CI/CD Pipeline for Multi-Environment Workflow Export and Deployment - n8n Workflow

• DevOps Engineers managing complex n8n infrastructure.


• n8n Automation Specialists needing reliable workflow version control.


• Teams practicing Infrastructure as Code (IaC) with their automation.


• Users looking for advanced n8n templates for Docker-based deployments.

Managing numerous n8n workflow configurations across different environments (Development, Staging, Production) can be challenging. This expert n8n workflow provides a structured solution by automating the export and staging process, making it essential for robust CI/CD pipelines.

This specific n8n automation leverages the n8n CLI and file system operations within the n8n node framework to export all active n8n workflows. It then standardizes the file naming (using the workflow name and ID) for readability and traceability. Crucially, the n8n workflow inspects the tags associated with each item. If a workflow contains a specific tag (e.g., 'Auto deploy to dev'), it is copied into a corresponding deployment folder, ready to be picked up by a Docker build process. This structure ensures that your n8n templates are always synchronized with your repository and deployed correctly to the intended environment.

This powerful n8n workflow is initiated by a manual n8n trigger and executes a sequence of file system and command-line operations to manage workflow exports:

1. Initiation and Setup: The 'Start export workflows' manual n8n trigger begins the process. The 'Create folders and run n8n cli' n8n node executes shell commands to clean up and create the necessary deployment directories (export/named-workflows, import-dev/workflows, etc.). It then runs the critical n8n export:workflow --all CLI command to export every existing n8n workflow.


2. Loading and Parsing: The 'load exported workflows' n8n node reads the newly created JSON files, and the 'parse workflow' n8n node extracts the content. The 'Remove root node' Set n8n node cleans the JSON structure, making it ready for file storage.


3. General Storage: The workflow is immediately stored in a general directory using a readable filename format (WorkflowName (ID).json) via the 'Create JSON file with readable name' n8n node.


4. Dev Deployment Staging: The 'TAG? Auto deploy to dev' If n8n node checks the item's tags for 'Auto deploy to dev'. If found, the n8n workflow is written to the ./import-dev/workflows folder, staging it for deployment to the development environment.


5. Prod Deployment Staging: Similarly, the 'TAG? Auto deploy to PROD' If n8n node checks for the production tag. If present, the n8n workflow is written to the ./import-prod/workflows folder, preparing it for a production deployment cycle.

This entire n8n workflow facilitates a robust, tag-driven multi-environment deployment strategy.

To install and use this advanced n8n workflow, follow these steps:

1. Import the JSON: Copy the provided n8n workflow JSON data and import it directly into your n8n instance via the 'Workflows' section using the 'New' -> 'Import from JSON' option.


2. Enable CLI Access: This n8n workflow relies heavily on the Execute Command n8n node accessing the n8n CLI (n8n export:workflow). Ensure that the user running your n8n container or instance has the necessary permissions to execute these commands and write to the local file system.


3. Docker Integration (Optional but recommended): For full CI/CD benefits, review the provided Sticky Notes which contain example Dockerfile and importing-docker-entrypoint.sh scripts. These files show how to configure your custom n8n Docker image to automatically import the staged workflows (import-dev/workflows or import-prod/workflows) at startup using the n8n CLI imports.


4. Tag Your Workflows: Ensure that the n8n workflows you intend to auto-deploy have the specific tags defined in the If nodes: 'Auto deploy to dev' or 'Auto deploy to PROD'.


5. Execution: Run the 'Start export workflows' n8n trigger manually to test the pipeline.

Start export workflows (Manual Trigger): Acts as the starting n8n trigger for the deployment pipeline, typically executed by a CI tool or an administrator.
Create folders and run n8n cli (Execute Command): This core n8n node handles file system preparation and workflow export. Key command: n8n export:workflow --all --output=export/n8n-workflows --pretty --separate.
load exported workflows (Read/Write File): Reads the raw, ID-named workflow JSON files exported by the CLI from the export/n8n-workflows directory.
Remove root node (Set): Transforms the data structure, extracting the actual workflow content using the expression ={{ $json.parsedData }} to clean up the metadata added by the n8n CLI export command.
TAG? Auto deploy to dev / PROD (If): Essential flow control n8n nodes. They check if the input item's tags ($json.tags.map((obj) => obj.name)) contain the specified deployment tag.
Create JSON file with readable name (Convert To File): This n8n node generates the binary file content, using an expression for dynamic filename creation: =./export/named-workflows/{{ $json.name }} ({{ $json.id }}).json.

• Store named workflow (Read/Write File): Performs the final write operation, saving the readable n8n workflow file to the appropriate environment-specific directory for deployment.