Understanding Workflow Publishing in n8n 2.0

Starting with n8n version 2.0, we've introduced a new workflow publishing system that replaces the previous active/inactive toggle. This means that the old "Activate/Deactivate" toggles become the new "Publish/Unpublish" buttons. This change gives you better control over when your workflow changes go live, reducing the risk of accidentally deploying work-in-progress changes to production.

What's Changed?

Before (v1.x): Active/Inactive Toggle

- Workflows had a simple toggle switch

- Saving an active workflow made changes live immediately

- Risk of accidentally deploying incomplete changes

Now (v2.0): Publish Workflow

- Save stores your changes without affecting production

- Publish explicitly makes your workflow live

- Clear separation between drafting and deployment

Workflow States

Unpublished Workflows

- Previously called "inactive"

- Won't execute automatically

- Safe for editing and testing

- Changes are saved but not live

Published Workflows

- Previously called "active"

- Execute normally based on triggers

- Your production version

- Remains running even while you edit a new version

Publishing Your Workflow

1. Make your changes in the workflow editor

2. Click Save to store your changes

3. Click Publish (top right corner) when ready to go live

4. Review the differences if needed

5. Confirm to make your changes live

Unpublishing a Workflow

To stop a workflow from running:

1. Click the three dots menu (⋮) in the top right corner

2. Select Unpublish

3. The workflow will stop executing (equivalent to "deactivate" in v1.x)

Sub-workflows and Error Workflows

Always publish sub-workflows and error workflows you intend to reference from other workflows. This prevents parent workflows from pulling in work-in-progress changes and ensures stability across your workflow ecosystem.

FAQ

Does Save make my changes live?

No. Save only updates the saved version of your workflow. Publish is what updates the live, executing version. This separation allows you to iterate safely without affecting production.

What happens when I unpublish a workflow?

Unpublishing stops a workflow from running, just like "deactivate" did in v1.x. You can unpublish a workflow by clicking the three dots menu (⋮) in the top right corner and selecting Unpublish.

Do parent workflows pick up in-progress sub-workflow changes?

No, not if you publish the sub-workflow properly. Parent workflows can only reference published versions of sub-workflows for stability. Unpublished (draft) versions are not visible to parent workflows. This is why it's important to publish sub-workflows and error workflows that other workflows depend on.

Can multiple people edit the same workflow at the same time?

Not at the moment. A single writer is enforced to avoid conflicts. More collaboration features are planned for future releases. If someone else is editing a workflow, you'll need to wait until they're done.

I can't find the active/inactive toggle anymore. Where did it go?

The toggle has been replaced by the Publish feature. Instead of toggling a switch, you now click Publish in the top right corner when you want your workflow to go live. This is an intentional change to give you more control over deployments.

Can I see what changed before I publish?

Yes! When you click Publish, you can review the differences between your saved version and the currently published version before confirming.

What happens to my currently active workflows after upgrading to v2.0?

Your existing active workflows will automatically be marked as published. You can continue using them normally. The new publishing system applies to any future edits you make.

Learn more: Workflow Publishing Documentation