Understanding Workflow Publishing and Unpublishing n8n 2.0
Starting with n8n version 2.0, workflow publishing replaces the previous Activate/Deactivate toggle. You now use Publish and Unpublish to control which workflow version runs in production.
This separates editing from deployment, so you can work on changes without immediately affecting your live workflow.
This article describes the current publishing experience. Some features and menu locations may differ on older versions of n8n.
What's changed?
Before: Active/Inactive toggle
Workflows used a toggle to activate or deactivate them.
Saving changes to an active workflow could make those changes live immediately.
Now: Drafts and publishing
Autosave stores your edits automatically, typically within 1–5 seconds. You don't need to click Save before publishing.
Publish makes a specific workflow version live in production.
Further edits remain in draft until you publish again, while the existing published version continues running.
Important exception: If you only update workflow settings, n8n automatically republishes the version without requiring you to click Publish. Don't treat settings changes as draft-only changes.
Learn more in Save and publish workflows.
Workflow states
Unpublished workflows
An unpublished workflow isn't enabled for automatic schedule, production webhook, or connected-app triggers. You can still edit and run it manually for testing.
Error workflows are an exception: workflows using the Error Trigger don't need to be published. See Error Trigger.
Published workflows
Production executions use the published version, not your latest draft edits. You can continue editing without replacing that version until you're ready to publish again.
Publishing status also matters: a published version doesn't necessarily mean every trigger activated successfully. Check the status described below.
Publishing your workflow
Make your changes in the workflow editor. n8n saves them automatically.
Click Publish in the canvas header, or press Shift + P, to open the publishing dialog.
The version name defaults to a UUID. Customize it if you'd like, and optionally add a description.
Click Publish in the dialog to publish that version.
Check the publishing status to confirm the outcome.
The standard publishing dialog is for naming and describing the version and confirming publication. It isn't a workflow-difference review screen.
Understanding publishing status
Publishing happens in the background. n8n applies trigger changes while unchanged triggers continue running.
Publishing: n8n is applying the changes and waiting for the result. Refreshing the page doesn't cancel publishing; the status is stored on the server.
Published, up to date: The workflow is published with no pending draft changes.
Published, has changes: Your production version is still published, but your newer edits aren't live yet.
Published, partial: The new version is published, but at least one trigger failed to activate. Other successfully activated triggers continue running. Hover over the button for details, resolve the reported problem, and publish again to retry.
Failed to publish: None of the workflow's triggers activated, so the workflow isn't running. The published version remains set, allowing you to publish again to retry.
Other states may indicate errors or changes that prevent republishing. See the publishing documentation for details.
Unpublishing a workflow
To remove a workflow from production, open the dropdown next to Publish in the canvas header and select Unpublish. You can also unpublish from the workflow list or version history page.
Unpublishing disables the workflow's automatic production triggers. You can continue editing and testing it manually.
Sub-workflows and error workflows
When working with dependent workflows, check their setup and execution behavior separately rather than assuming all workflow types follow the same publishing rules.
Sub-workflows: Follow the sub-workflow documentation when configuring a workflow called by another workflow. Test the parent and sub-workflow together before deploying changes.
Error workflows: A workflow using the Error Trigger doesn't need to be published. The Error Trigger runs when an automatic workflow errors; it doesn't run when you're testing a workflow manually. See Error Trigger.
Workflow reviews
If workflow reviews are enabled on your instance, you can submit a version for review instead of publishing it immediately. An open review blocks publishing that workflow until the review is resolved. Approval normally publishes the reviewed version automatically.
Workflow reviews are available from n8n 2.37.0 on Enterprise Cloud and self-hosted Enterprise and must be enabled by an instance admin. The feature is currently in Preview; the documentation advises against relying on it in production workflows.
Reviews include a Changes tab with a visual comparison between the published version and the version submitted for review. This is separate from the standard publishing dialog.
Learn more in Workflow reviews.
FAQ
Do I need to save before publishing?
No. n8n saves your edits automatically. There's no required manual Save step before clicking Publish.
Does autosave make my changes live?
Autosaved edits to workflow nodes and connections remain in draft until you publish. However, settings-only updates automatically republish the version without a separate Publish action.
Can I see what changed before publishing?
The standard Publish dialog asks for a version name and optional description, not a diff review. If your instance supports and has enabled Workflow reviews, the review's Changes tab provides a visual comparison. See Workflow reviews for availability and limitations.
Can multiple people edit the same workflow at the same time?
Only one person can edit a workflow at a time. Other users see it in read-only mode. The editing lock releases when the editor stops editing or becomes inactive, allowing someone else to take over with the latest changes.
Why is the Publish button disabled or publishing blocked?
The button may be disabled when there are no publishable changes. Errors or invalid changes may also prevent republishing. If a workflow has an open review, publishing is blocked until the review is resolved. Check the status shown in the editor for details.
What if my workflow stays in Publishing?
Publishing is asynchronous, so the Publishing state doesn't by itself indicate a problem. Allow the process to finish and check for a result. Reloading the page won't reset an in-progress publication.
If the state persists unexpectedly, contact support with your n8n version, the workflow ID, when publishing started, and any visible error message or screenshot. For self-hosted instances, include relevant server logs, with credentials and other sensitive information removed. Don't assume the workflow is running successfully until its publishing outcome is confirmed.
Where did the Active/Inactive toggle go?
It was replaced by Publish and Unpublish. Use Publish to deploy a workflow version and Unpublish to disable its automatic production triggers.
Learn more
n8n v2.0 breaking changes — additional guidance for users upgrading from v1.x.
Learn more: Workflow Publishing Documentation