# How to deploy changes to a workflow? **URL:** \ **Category:** Questions\ **Created:** [September 16, 2024, 10:54pm UTC](https://community.n8n.io/t/how-to-deploy-changes-to-a-workflow/54301 "2024-09-16T22:54:00Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![shot](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/shot/32/8139_2.png) [@shot](https://community.n8n.io/u/shot)\ **Post date:** [September 16, 2024, 10:54pm UTC](https://community.n8n.io/t/how-to-deploy-changes-to-a-workflow/54301/1 "2024-09-16T22:54:00Z")
Greetings! I’m new to n8n and have a really basic question about development best practice. How exactly do I “deploy” workflow changes to live/production? Am I correct that saved changes are immediately “live” for an active workflow? I was kind of expecting an explicit “deploy to live” action somewhere that would push changes after they’ve been thoroughly tested, but maybe I need to adjust my mental model. I searched the docs and forum, so I think I’m missing something really fundamental. Thanks for any info or insights. ## Information on your n8n setup - n8nVersion: 1.58.2 - platform: docker (self-hosted) - nodeJsVersion: 20.15.0 - database: postgres - executionMode: regular ---
**Author:** ![n8n](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/n8n/32/196425_2.png) [@n8n](https://community.n8n.io/u/n8n)\ **Post date:** [September 16, 2024, 10:54pm UTC](https://community.n8n.io/t/how-to-deploy-changes-to-a-workflow/54301/2 "2024-09-16T22:54:01Z")
It looks like your topic is missing some important information. Could you provide the following if applicable. - **n8n version:** - **Database (default: SQLite):** - **n8n EXECUTIONS\_PROCESS setting (default: own, main):** - **Running n8n via (Docker, npm, n8n cloud, desktop app):** - **Operating system:** ---
**Author:** ![shot](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/shot/32/8139_2.png) [@shot](https://community.n8n.io/u/shot)\ **Post date:** [September 16, 2024, 11:42pm UTC](https://community.n8n.io/t/how-to-deploy-changes-to-a-workflow/54301/3 "2024-09-16T23:42:21Z")
> [@n8n](#): > > - **n8n EXECUTIONS\_PROCESS setting (default: own, main):** default > - **Operating system:** macOS and Ubuntu VPS Not sure where to find the first item, so I’m assuming default. The rest is in my original post. ---
**Author:** ![bartv](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/bartv/32/156374_2.png) [@bartv](https://community.n8n.io/u/bartv)\ **Post date:** [September 17, 2024, 7:45am UTC](https://community.n8n.io/t/how-to-deploy-changes-to-a-workflow/54301/4 "2024-09-17T07:45:08Z")
That is correct - changes are deployed when saved. Our Enterprise plan supports different environments, like dev/test/staging/prod: > **[n8n Plans and Pricing - n8n.io](https://n8n.io/pricing/)** > > Discover n8n's pricing alternatives for cost-effective workflow automation solutions. Find the perfect plan to maximize your workflows. ---
**Author:** ![shot](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/shot/32/8139_2.png) [@shot](https://community.n8n.io/u/shot)\ **Post date:** [September 17, 2024, 12:40pm UTC](https://community.n8n.io/t/how-to-deploy-changes-to-a-workflow/54301/5 "2024-09-17T12:40:45Z")
> [@bartv](#): > > changes are deployed when saved Thanks for the quick reply, @bartv, but my question remains. For those not on the Enterprise plan, what’s the recommended way to deploy changes without taking a workflow offline? If I have a critical workflow, how do I update it and thoroughly test it before making it live? The only thing that comes to mind is to duplicate it, make and test the changes, and then activate the duplicate before deactivating the original. Is that the best way? ---
**Author:** ![sfx](https://avatars.discourse-cdn.com/v4/letter/s/c37758/32.png) [@sfx](https://community.n8n.io/u/sfx)\ **Post date:** [September 17, 2024, 12:56pm UTC](https://community.n8n.io/t/how-to-deploy-changes-to-a-workflow/54301/6 "2024-09-17T12:56:56Z")
hello you can just clone the workflow 🙂 ---
**Author:** ![bartv](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/bartv/32/156374_2.png) [@bartv](https://community.n8n.io/u/bartv)\ **Post date:** [September 17, 2024, 1:26pm UTC](https://community.n8n.io/t/how-to-deploy-changes-to-a-workflow/54301/7 "2024-09-17T13:26:22Z")
sfx is correct; you can duplicate a workflow from the menu on the top-right of your screen. Alternatively, I suppose you could create a workflow that uses that uses the [n8n node](https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.n8n/) to fetch a workflow and create a duplicate, and after testing, overwrite the ‘live’ version with the tested one (that would in fact be a cool thing to try!) ![image](https://europe1.discourse-cdn.com/n8n/original/3X/b/3/b36c934846dd2b5b165fb3150b7b0ef209a684b5.png) ---
**Author:** ![shot](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/shot/32/8139_2.png) [@shot](https://community.n8n.io/u/shot)\ **Post date:** [September 17, 2024, 2:19pm UTC](https://community.n8n.io/t/how-to-deploy-changes-to-a-workflow/54301/8 "2024-09-17T14:19:04Z")
Ok, thanks for the replies! So basically, what I said… > [@shot](#): > > The only thing that comes to mind is to duplicate it ### EDIT > [@bartv](#): > > create a duplicate, and after testing, overwrite the ‘live’ version with the tested one Just a quick edit to note that I was thinking along those lines as well. I’d use my local machine for development and testing, though, and then overwrite the live workflow via the API. 🙂 👍 Thanks again. ---
**Author:** ![system](https://dub1.discourse-cdn.com/n8n/user_avatar/community.n8n.io/system/32/195824_2.png) [@system](https://community.n8n.io/u/system)\ **Post date:** [September 24, 2024, 2:20pm UTC](https://community.n8n.io/t/how-to-deploy-changes-to-a-workflow/54301/9 "2024-09-24T14:20:05Z")
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.