Saving & Publishing
The workflow builder saves your edits automatically as a draft. Click Publish when you want those changes to become the version used by published runs. Editing an already published workflow creates a draft while its last published version remains available.
Choose the right action
Save and test your draft
Change the workflow’s name, description, nodes, or connections in the builder. Edits save automatically after a short pause or when you leave a field. If a save error appears, resolve it before leaving the page.
Click Run in the builder header, or open its dropdown and choose Run current workflow. If the Start node defines inputs or accepts files, fill in the input dialog before starting. The debugger opens so you can step through the run and inspect its results. See Testing & Debugging for breakpoints and overrides.
Debug runs perform real actions, including sending messages and updating external systems. Use test recipients and data, or configure overrides for steps you do not want to execute.
Publish changes
- Review the nodes, credentials, and Start node settings.
- Click Publish in the builder header.
- If the check reports an error, correct the named node or field and publish again.
- Wait for the publication confirmation before relying on the new version.
Publishing also applies configured Gail webhook and workflow-tool changes. If publication succeeds but a webhook or tool update fails, the workflow is published, but that integration still needs attention. Follow the error message and publish again after resolving the problem.
Run the published version
Open the dropdown next to Run and select Run last published. This option is unavailable until the workflow has a published version. Provide any requested inputs or files, then start the run.
Use this action to check the version currently in use while keeping a draft for further edits. Changes to shared Public Variables and Secret Variables are saved separately from the workflow draft. Manually started published runs can therefore use updated shared values even when you have not republished the workflow. Scheduled workflows require republishing to refresh those values.
Discard an unpublished draft
If a published workflow has draft changes, the builder shows Revert to Published. Click it and confirm that you want to discard the draft. The builder reloads the last published workflow.
This discards your unpublished changes. It does not undo actions performed by earlier runs or roll back separately saved public variables and secrets. It also does not select an older published revision; it returns to the most recently published version.