Site icon JD Bots

How to Publish a Workflow in n8n

Card titled How to Publish a Workflow in n8n, labelled n8n Tutorial how-to, showing a workflow named Runs every minute with a Published badge, a clock node and three succeeded runs at 11:09, 11:10 and 11:11.

A workflow in n8n doesn’t run on its own until you publish it. Publishing makes it live: schedules start running, and form and webhook triggers switch to their production addresses. This guide shows how to publish a workflow in n8n, check that it runs, publish a change, and unpublish it to stop it.

The example is the smallest workflow that shows the difference: one Schedule Trigger node that runs every minute.

Cost: free. Publishing is part of n8n’s free Community Edition.

Every screen on this page is real, from n8n 2 running in Docker on macOS.

Step 1: Create a Workflow That Runs Every Minute

Click + at the top of the left sidebar, then New workflow. Click the name My workflow at the top, type a new one, here Runs every minute, and press Enter.

Click Add first step in the middle of the canvas, then On a schedule. Set Trigger Interval to Minutes and Minutes Between Triggers to 1. The yellow note says it plainly: the workflow runs on this schedule once you publish it.

Every 1 minute, live once published.

Close the panel. n8n saves your changes as you work, so there’s no Save button. The Publish button at the top right is now active.

Publish is active.

Step 2: Publish the Workflow

Click Publish (or press Shift + P). The Version name starts as “Version” and a short code; give it a name you’ll recognise, such as First version, and say what changed under Describe changes. Click Publish.

Name the version, then click Publish.

n8n confirms Workflow published: the schedule trigger now starts runs on its own. Click Got it.

n8n confirms the workflow is live.

The button now reads Published, with a green dot.

Published, with a green dot.

Step 3: Check That It Runs

Click the Executions tab above the canvas. Each minute adds a run to the list; these are real production runs, started by the schedule.

A new run every minute, from the published version.

Step 4: Publish Your Changes

Edits to a published workflow are saved, but they don’t go live on their own. To see this, open the Schedule Trigger node, change Minutes Between Triggers to 2 and close the panel. The button turns into Publish with an amber dot, which means there are changes that aren’t live yet. Until you publish them, the runs keep coming every minute, from the published version.

Amber dot: changes not live yet.

Click Publish again, name the new version (here Every 2 minutes) and click Publish. The button goes back to Published.

Step 5: Unpublish to Stop It

Click the arrow next to Published, then Unpublish (or press Ctrl + U, ⌘ + U on a Mac), and confirm.

The arrow next to Published, then Unpublish.
Confirm with Unpublish.

The button shows Publish again, as it did before you first published, and the schedule stops starting new runs.

Clean Up

The example runs until you unpublish it, so do Step 5 first. Then remove it: click ⋯ next to the workflow name, then Archive.

The three-dot menu, then Archive.

n8n hides archived workflows from the list. Click Update filters to show them, open Runs every minute, click ⋯ again, then Delete.

Once archived, Delete appears.

Warning: deleting removes the workflow permanently.

Confirm with Yes, delete.

Confirm with Yes, delete.

Common Mistakes

MistakeWhat happensDo this instead
Expecting a schedule to run before you publishNothing runs: schedules start only once the workflow is publishedPublish the workflow
Editing a published workflow and stopping thereYour edits are saved, but the schedule keeps running the published versionPublish again to put the changes live

Troubleshooting

ProblemCauseFix
Publish is greyed outThere’s nothing to publish yet, for example a new workflow with no triggerAdd a trigger, or make a change, then publish

FAQ

Do I need to publish a workflow to test it?

No. The Execute button at the bottom of the canvas runs it once for testing, and test runs don’t need publishing. Publish when the workflow should run on its own.

What does publishing change for form and webhook triggers?

They switch from their test address to their production address, which works while the workflow is published (n8n’s publishing guide).

Can I name the versions I publish?

Yes: the Publish dialog lets you name the version you publish. Naming other versions from the version history is a paid feature (Business or Enterprise when self-hosted, per n8n’s docs).

Where can I see which workflows are published?

In the Workflows list, published workflows show an indicator on their card.

Conclusion

Publishing puts a workflow live: click Publish, name the version, and its trigger starts runs on its own. Publish again after every change you want live, and unpublish to stop it.

Additional Resources

Related

n8n and other names mentioned are trademarks of their respective owners. JD Bots isn’t affiliated with or endorsed by n8n GmbH.

Exit mobile version