Make
Save as version gives Make builders a way to label saved scenario states, review them in a readable changelog and restore an earlier version. The update removes the need to clone scenarios purely to test and iterate, or rely on memory to track what changed.
The LinkedIn announcement also introduces a refreshed scenario editor toolbar. Run once and Save now sit together, while scheduling and the Active/Inactive toggle have moved to the top right.
| Area | What changed |
|---|---|
| Testing and saving | Run once and Save now sit side by side |
| Scheduling | Controls have moved to the top right |
| Activation | The Active/Inactive toggle is now in the top right |
| Version history | Saved states can include custom descriptions and be restored |
Save as version Creates a Readable Changelog
Selecting Save as version lets a builder add a custom description to the saved state. Version history is available from the bottom toolbar, where those descriptions appear as a readable record of previous changes.
From there, builders can review earlier descriptions and restore a previous version. This gives teams a record of what was saved as a scenario changes, rather than requiring separate cloned scenarios for each round of testing.
Descriptions are written by the person saving the version. They can therefore record the purpose of a change, such as adjusting a filter, replacing a connection or testing a different route through the scenario.
The Toolbar Separates Editing From Activation
The toolbar refresh groups controls around different stages of scenario work. Run once sits beside Save for testing and editing. Scheduling and the Active/Inactive toggle remain available in the top-right corner, away from the main building controls.
The underlying actions have not changed in the announcement. The update reorganises where builders find them and adds named saved states to Version history.
Together, the toolbar and version controls cover testing, saving, reviewing and restoring scenarios inside the editor. Teams can keep previous states in Version history instead of maintaining extra scenario copies for iteration.
Frequently asked questions
What is Save as version in Make?
Save as version is a scenario editor feature that saves a state with a custom description. Those saved states appear in Version history, where builders can review the descriptions and restore previous versions.
How do I restore a previous Make scenario version?
Open Version history from the bottom toolbar and review the saved descriptions. Select the previous version you want to restore.
Which Make plans include Save as version?
Plan availability was not included in the announcement. No separate pricing information was provided.
Sources
4 checkedHow we cover tool news: Create With's tool desk drafts these reports with AI from the sources listed above and checks them against those sources before publishing.
ElevenLabs
Notion
