Overview
Draft Versions let you build and edit your workflows without affecting the version that's running live. Your changes are saved to a draft until you choose to publish them, so your active automations keep running untouched while you work.
This article explains how draft versions work, both when you're creating a new workflow and when you're editing one that's already published.
Creating a new workflow
When you create a new workflow, it starts in draft mode automatically. As soon as you begin building - adding triggers, actions, and other steps your work is saved to the draft. Nothing runs live until you publish it.
All of your changes are tracked and stay on the draft version. You can confirm you're working in a draft from the "Unpublished changes" label and the version control icon.
Publishing your workflow
When you've finished editing and testing your workflow and you're happy with it, click Publish. All of your draft changes are promoted to live at once.
Editing a published workflow
When you edit a workflow that's already published, your changes are not applied to the live version. Instead, they're saved to a new draft, so the published workflow keeps running exactly as it is.
You can see this in two places:
- The "Unpublished changes" label, indicating you have edits that aren't live yet.
- The version control, where your draft version (with your in-progress changes) appears alongside the published version that's still running live.
Publishing your updates
Once you've finished your changes and you're ready to make them live, click Publish changes (v{number}). Your updates are promoted to live as a new version, so your published workflow only ever changes when you choose to publish.
Good to know
- A workflow only ever goes live when you click Publish - your changes are never applied automatically.
- The "Unpublished changes" label is your quick check for whether you have draft edits waiting to be published.
- Publishing a previously published workflow creates a new version, so you have a record of each published change.
- Webhook urls are being displayed only on published workflows on the publish button as a workflow needs to be published in order to get data from webhooks.