Clone a scenario and keep every note right where you need it
When you duplicate a scenario in Make, you are not just copying modules and routes anymore. You are carrying over the thinking behind the build too, so the next version starts with the same context, instructions, and reminders already in place.
Copy scenario notes when cloning a scenario is now here. When you clone a scenario in Make, the associated notes come with it, just like they already do in export and import flows. Your cloned scenario now includes the same written context as the original, from setup tips to team handoff details.
What’s new
Notes move with the clone: Make now copies associated notes as part of the cloning action, so the new scenario starts with the same comments, instructions, and build guidance.
Key benefits
-
Templates keep their playbook: If you use one scenario as a base for many others, each copy brings the notes that explain naming rules, variable mapping, or what to adjust before going live. -
Team handoffs stay clear: The details your teammate needs, like why a filter exists or what a webhook expects, stay attached to the cloned version instead of living in a separate message thread. -
Testing gets cleaner: Spin up a copy for experiments, QA, or client-specific edits while keeping the original guidance visible in the exact place the work happens.
Real-world use cases
-
Build once, reuse many times: Agencies and ops teams can clone a proven scenario for each client or region and keep setup notes inside every copy. -
Create safe test versions: Before changing routing, formulas, or error handling, clone the scenario and keep all internal notes in the test version for faster reviews. -
Hand off work without extra docs: When one Maker builds and another maintains, the cloned scenario already includes the context needed to pick up the next step with confidence.
Happy automating! 
Valery from Make
Helpful resources