Save and Publish Workflows

Save keeps your draft. Publish makes a valid version available for execution. Manual runs, schedules, and webhook requests use the published version.

Prepare the draft

1. Configure one trigger and its filters.
2. Connect the actions and branches in the intended order.
3. Fill required fields and resolve validation warnings.
4. Select Test workflow and review the simulation.
5. Select Save.

Simulation does not send messages or modify records. Use it to check configuration before enabling real execution.

Publish and verify

Select Publish when the draft is ready. Fix the listed issues if publication is blocked. Publishing an event-triggered workflow enables matching events to start it, so check filters and recipients first.

For manual, webhook, and scheduled triggers, configure the trigger resources after saving and publishing. Run one controlled example and inspect its run detail and actual outputs before increasing volume.

Update an existing workflow

Edit the draft, simulate the changed paths, save, and publish the new version. Saving alone does not replace the published version. Runs retain the version they started with; review active runs separately after major changes.

If an existing automation is producing incorrect results, stop its incoming triggers or pause the available schedule before making further changes. Editing a draft does not undo earlier actions.

See Workflow runs to verify the executed version and step results.