Publishing makes your draft the version that runs. Bizomate checks every step first; once nothing stands in the way, you can add a short note saying what changed, and the draft goes live at once.

Who can do this

Workspace Admins and Editors. Workflows with Code, HubSpot or Microsoft SQL steps need a paid plan to publish — see If something goes wrong.

Before you start

Test the workflow. Not tested does not block publishing, but a test is the only way to see it work. See Testing a workflow before you publish it.

Steps

  1. Open the workflow in the designer.
  2. Select Publish at the top right. The button reads Checking while Bizomate looks over every step.
  3. If something needs finishing, a panel opens under Publish — for example 2 steps need setup, Publishing saves a version. These two would fail the moment it ran, so they have to be finished first. Each line names the step and what is missing.
    • Select Go to step to open that step's settings. Fields still empty now say Fill this in before publishing.
    • Fix each one, then select Publish again. See Fix steps marked Needs setup.
  4. When nothing stands in the way, Publish v3 opens: v3 goes live straight away and Live v2 becomes a version you can compare or restore.
  5. Optional: in What changed?, type a short note — up to 120 characters — such as Sends the summary to Asha as well. Shown beside v3 in Versions. Left empty, the version shows only when it was published and by whom.
  6. Select Publish v3. The button reads Publishing while it works.

A toast says Published as v3 and, depending on the workflow's switch:

  • It runs from its next trigger. Keep editing — changes stay in the draft until you publish again.
  • It is switched off, so it will not run until you switch it on from the Workflows list.

What happens next

  • The draft becomes the live version, and a new draft opens above it with the same steps. Keep editing — nothing live changes until you publish again.
  • A first publish switches the workflow on, unless the plan's limit of workflows switched on is already reached.
  • The trigger is set up for the live version:
    • A schedule starts counting in your time zone — the publisher's.
    • A webhook's Production URL starts answering. It stays the same across publishes.
    • A form is given its address, made from its title, and opens.
    • An app trigger starts checking. Only what arrives after publishing starts a run.
  • The workspace's other Admins are notified: … published as v3 — Consulace workspace, by Rohan Mehta.
  • Older versions beyond what the plan keeps are removed — 3 on Free, 10 on Starter, 100 on Pro, every version on Enterprise. The live version and the draft are always kept.

Good to know

  • There is no unpublish. To stop a workflow, switch it off — see Publishing a workflow versus switching it on.
  • Publishing checks Production values. A variable with a Development value but no Production value stops publishing, whatever Test in: says.
  • Paid steps can be built and tested on Free. Publishing is where a paid plan starts, because that is when they run on their own.

If something goes wrong

What you see Why What to do
1 step needs setup (or more) A step is missing a connection, a required setting, a variable value or a permission. Select Go to step and finish it. See Fix steps marked Needs setup.
Not ready to publish — Publishing saves a version, and this one could not run yet. Something about the whole workflow: Add a trigger — how the workflow starts., Add at least one step after the trigger., or The plan allows 20 steps in a workflow, and this one has 22. Do what the line says.
2 steps need a paid plan — You built and tested these on Free, which is how it should be. Publishing is where a paid plan starts, because that is when they run on their own. The workflow has Code, HubSpot or Microsoft SQL steps — or an HTTP Request sending through a paid connection. Select See plans (company Owner only), or remove those steps and publish the rest. Others see Only the company's owner can change the plan.
Published as v3 — It is switched off: the plan's running limit is reached. Switch another off on the Workflows list to run this one. A first publish, with the plan's limit of workflows switched on already reached. Switch another workflow off, then switch this one on.
Not published — Something went wrong. What is live has not changed. Publishing did not complete. Try again.