---
title: "Clone a flow instead of rebuilding it: Save As is the shortcut everyone skips"
date: 2026-08-08T00:00:00Z
updated: 2026-09-11T11:47:29Z
tags: ["Power Automate", "Automation", "Efficiency"]
canonical: https://bianca.codes/blog/clone-a-flow-instead-of-rebuilding-it/
---

# Clone a flow instead of rebuilding it: Save As is the shortcut everyone skips

_Save As duplicates a flow, trigger, actions and conditions in one move, turning a rebuild into a two-minute edit._

You've built a flow. Now you need one that's 90% the same, except it watches a different SharePoint list, or the digest goes to a different distribution group. The instinct is to open a blank canvas and start dragging in triggers again. The three-click move is Save As, and it clones everything, trigger included, so you're editing instead of rebuilding.

## How to do it

Open **My flows**, hover over the flow you want to copy, and click the ellipsis menu (the same command also lives in the top toolbar of the flow's Details page, and in the toolbar once you've selected the flow's checkbox).

Choose **Save As**, not Save. Save edits the flow you have open; Save As creates a new one from it.

Give the copy a name that says what's different, not "Copy of X". Six months from now, "Copy of X" tells you nothing.

The new flow saves turned off by default. Leave it off until you've actually made your edit, then turn it back on from the same ellipsis menu.

## Why it works

Save As doesn't rebuild the flow from a description of what it does. It duplicates the underlying flow definition wholesale, trigger and all, because Power Automate is copying the JSON that defines the flow rather than regenerating it from scratch. Every condition branch and every expression that references a previous step's output comes across intact.

That's also why the copy lands disabled. Two flows built from an identical trigger, both live at the same time, will both fire on the same event. Turn on the copy before you've changed the recipient or the source list, and you've got duplicate emails or duplicate rows to clean up instead of the one edit you meant to make.

## When not to use it

Save As is not automatically a clean handoff to someone else. If a colleague needs to own the copy and it runs on a connection tied to your account, your mailbox or your OneDrive, they'll need to re-authorise those connections under their own name before it can run reliably as theirs, not yours.

And if the thing that keeps changing between copies is a value, a folder path, a distribution list, a threshold, cloning the flow every time that value changes is a sign the value belongs in a variable the flow reads, not something you hand-edit in a fresh copy each time.