The flow builder header contains the controls you use most often while building: saving your work, switching between building and testing modes, and seeing who else is editing the automation at the same time.
Saving
Edits to an automation are not automatically saved. Click Save in the header to persist the current state as a draft. Where enabled, Save & Close saves and returns you to the automations list. Unsaved changes are visible only to you; other collaborators and any running instances of the automation continue to use the last saved (and deployed) version.
Note: Saving creates a new draft version. Deploying is a separate action — a saved automation is not live until it is deployed.
Note: There is no explicit locking mechanism or automatic merge when multiple users edit the same automation. If two users save at the same time, the last save wins — the version saved second overwrites the version saved first. To avoid unintentionally overwriting a collaborator's changes, check the live collaborator avatars in the header and coordinate with other editors before saving.
Build / Test Toggle
The Build / Test toggle in the header switches between the two views:
Build — the canvas where you add, configure, and connect steps.
Test — the test view, visible if you have test access, where you can run the automation with sample input and inspect results step by step.
Switch freely between the two as you develop. The toggle is only visible when both views are available for your access level.
Deploy Controls
Once an automation has been deployed at least once, the header also shows:
Running / Paused switch — pause or resume the live automation without undeploying it. Pausing stops new trigger-based runs from starting; in-flight runs finish normally.
Deploy button — publishes the current saved draft as the live version, replacing the previously deployed version.
Live Collaborators
The header shows avatar icons for any other collaborators currently editing the same automation. Each avatar represents a person who has the automation open in the builder. Hovering over an avatar shows their name.
Unify Automations supports live, simultaneous editing — multiple people can be in the builder at once. Changes made by one editor are visible to others after they save. There is no explicit locking mechanism, so communicate with collaborators before making large structural changes to avoid overwriting each other's work.
Notes
Keep the following in mind when working with save, build/test, and collaborator controls:
Save frequently; there is no auto-save.
Deploy and Save are independent — always save before deploying to make sure the deployed version reflects your latest changes.
The Running / Paused switch and the Deploy button are only visible for automations that have been deployed at least once.
Treating Save and Deploy as distinct, deliberate steps prevents work-in-progress changes from going live before they are ready.