Cross-Instance Workflow Synchronization Utility - n8n Workflow

Automation Architects managing multiple staging and production n8n environments.
Technical Teams needing to deploy consistent n8n workflow updates across different self-hosted instances.
Users who want a reliable method to back up or move specific n8n templates between accounts.
Anyone utilizing the n8n API for administrative and DevSecOps tasks.

Managing multiple n8n instances often leads to synchronization challenges. Manually exporting and importing complex n8n workflow definitions is time-consuming and error-prone. This specialized n8n workflow solves this by automatically identifying and cloning workflows present in a source instance but missing from a destination instance.

By leveraging the native n8n node functionality and SQL comparison logic within the Merge node, this automation ensures high fidelity synchronization. After cloning the missing n8n workflow, it uses an advanced HTTP Request step to optionally assign the new workflow to a specific project on the destination instance, offering complete administrative control over your new n8n templates deployment.

This automation starts with the 'When clicking Test workflow' n8n trigger.

1. Retrieve Workflows: The n8n workflow immediately branches, simultaneously querying the GET - Workflows n8n node for the source instance's workflows and the GET - Destination Workflows n8n node for the destination instance's workflows.


2. Prepare Data: The data from both instances is separated using the Split Out Workflows n8n node variants.


3. Identify Missing Workflows: The core logic resides in the Merge Workflows n8n node, which uses a SQL LEFT JOIN comparison. It compares the workflow names from the source (Input 1) against the destination (Input 2). The WHERE input2.name IS NULL clause ensures that only workflows that exist in the source but are missing from the destination are passed forward.


4. Batch Processing: The Loop Over Items n8n node processes the identified workflows in small batches (5 items per batch).


5. Create Workflow: For each missing workflow, the CREATE - Workflow n8n node utilizes the n8n API credential for the destination instance to re-create the workflow, including its nodes, connections, and settings.


6. Project Assignment (Optional): Following creation, the workflow dynamically finds a target project ID on the destination instance using HTTP Requests and filtering. Finally, the PUT - Workflow in Project n8n node transfers the newly created n8n workflow into the specified project.

To deploy this powerful n8n workflow and manage your n8n templates, follow these steps:

1. Import the JSON: Copy the provided n8n workflow JSON code and import it into your n8n instance using the 'New' menu -> 'Import from JSON'.


2. Source Instance Credential Setup: Locate the GET - Workflows n8n node. Update the 'n8n API' credential (labeled 'AK n8n original account' in the template) to point to your Source n8n instance.


3. Destination Instance Credential Setup: Update the 'n8n API' credentials used by GET - Destination Workflows and CREATE - Workflow (labeled 'AlexK1919 n8n ent account' in the template) to point to your Destination n8n instance.


4. API Keys: Ensure the credentials configured have the necessary permissions (usually All permissions) to list and create n8n workflow items.


5. Configure Project Filter (Optional): If you wish to use the project assignment feature, navigate to the Filter Project n8n node and change the rightValue in the condition to match the exact name of the project you want the new n8n workflow to be transferred to on the destination instance.

This n8n workflow relies on core nodes and the n8n API:

When clicking ‘Test workflow’ (Manual Trigger): The essential n8n trigger to initiate the cloning process. Used for immediate synchronization tests.
GET - Workflows / GET - Destination Workflows (n8n node): Uses the n8n API resource to retrieve all workflows from the respective source and destination instances.
Merge Workflows (Merge node): Crucial for logic control. Uses Combine by SQL mode with a LEFT JOIN to filter out any n8n workflow that already exists on the destination instance based on the workflow name.
CREATE - Workflow (n8n node): The final action node, responsible for posting the complete JSON definition of the missing n8n workflow to the destination instance's API.
Filter Project (Filter node): Used to identify a specific Project ID on the destination instance by matching the project name (e.g., 'z Original n8n Workflows from AlexK1919').
PUT - Workflow in Project (HTTP Request node): An advanced utility n8n node that makes an API call to transfer the newly created n8n workflow into a specific project container.