How to Copy and Paste Power Automate Actions (2026)

Rebuilding a configured Power Automate action because the copy controls have moved is maddening. Here is the short answer.

To duplicate an action in a cloud flow, right-click the action and select Copy action. Right-click the destination +, then select Paste an action. Power Automate supports both individual actions and container actions such as Scope and Condition. It does not document a supported way to paste arbitrary raw JSON into the cloud flow designer.

That last distinction is where a great deal of Power Automate advice goes wrong.

Fact-checked against Microsoft Learn on 7 August 2026.

Choose the right kind of copy

What you need to reuse	Safest supported method
One action in the same cloud flow	Copy action and Paste an action in the new designer
One action in the classic designer	Copy to my clipboard, then select it from My clipboard
A Scope, Condition or other container with its nested actions	Copy the container action
An action in a different cloud flow	See the cross-flow warning below; Microsoft's current pages disagree
A complete flow for your own use	Save As
A complete flow for another person	Send a copy
One non-solution flow moving between environments	Export and import a .zip package
Flows moving through development, test and production	Use a Power Platform solution
Actions from a Power Automate Desktop subflow	Copy the subflow actions as text; desktop flows use a different mechanism
Raw cloud-flow action JSON from a text file or forum	There is no documented native import; read Can You Import JSON Actions into Power Automate?

How to copy and paste an action in the new designer

Microsoft's current procedure is short:

1. Open the cloud flow in the Power Automate designer.
2. Right-click the action you want to reuse.
3. Select Copy action.
4. Right-click the + where the copied action should go.
5. Select Paste an action, then Paste an action again if the menu asks you to confirm it.
6. Review the copy, save the flow and test it.

The pasted action normally has -copy appended to its name. Microsoft also documents Ctrl+C and Ctrl+V as keyboard alternatives.

See Microsoft's illustrated copy-and-paste instructions in the cloud flow designer.

What can be copied?

Microsoft separates copyable steps into two groups:

• Atomic actions, such as Compose, Get items and Create item.
• Container actions, such as Scope, Switch, Condition and Apply to each.

Copying a container copies the actions nested inside it. This is the supported way to move a block that is already grouped inside a Scope or Condition; you do not need to recreate every nested action separately.

Microsoft's workflow creation guidance also says that individual actions, conditions and Scope actions can be copied.

Do not treat a successful paste as a finished flow

A pasted card proves only that Power Automate created the card. Before relying on it, check:

• the connector and selected connection;
• dynamic content taken from earlier steps;
• expressions that refer to action names;
• SharePoint site, list, mailbox, table, folder and environment-specific values;
• Run after settings;
• nested branches and loop inputs;
• secure input and output settings;
• the result of a real test run.

This matters most when the source action depends on steps that do not exist at the destination.

How to use My clipboard in the classic designer

My clipboard is the classic designer's action-copy interface. It is not the label used by the new designer.

1. Select the action's ellipsis (…) menu.
2. Select Copy to my clipboard.
3. Select New step or the destination +.
4. Open the My clipboard tab.
5. Select the copied action.
6. Recheck its connections, inputs and dynamic content before saving.

Microsoft still documents these steps in its classic-designer copy guidance.

The classic designer is in maintenance mode, while Microsoft's future development is focused on the new designer. It remains useful when an existing flow cannot yet be edited reliably in the new interface.

Can you copy an action to another flow?

Sometimes—but Microsoft currently gives contradictory instructions. Do not assume cross-flow copy will work in the new designer until you have tested it in your own environment.

As of 7 August 2026:

• the cloud flow designer page says actions can be copied between flows;
• Microsoft's workflow creation guidance also describes reuse across flows;
• the classic versus new designer comparison says the new designer does not support copy and paste across browser tabs or flows, while the classic designer does.

Those statements cannot all be true in every tenant and browser session.

The dependable rule is:

• use the new designer for copying within the same flow;
• if cross-flow paste fails, switch the source and target to the classic designer where that option is available;
• for a large block or a complete flow, use Save As, Send a copy, a package or a solution instead of fighting the clipboard.

This is a documentation gap, not evidence that you have missed a hidden setting.

Can you copy a trigger?

Do not plan on copying a trigger. Recreate and configure the trigger in the destination flow.

Microsoft's workflow creation page explicitly says triggers cannot be copied. A separate designer page currently tells readers to right-click an “action (or trigger)”, so the official pages disagree here too.

The conservative approach is to copy actions only. A trigger controls how a flow starts and often contains flow-specific connection, concurrency and split-on settings. Rebuilding it deliberately is safer than assuming a pasted trigger is supported.

Can you copy multiple actions at once?

Yes, when those actions are inside a supported container. Copy the Scope, Condition, Switch or Apply to each rather than copying every child action individually.

This works well for a self-contained block. It is less reliable when actions inside the container refer to steps outside it. Those external references still need to exist and make sense at the destination.

Do not add a Scope to a production flow solely to create a makeshift snippet library without retesting the flow. If the block is large or reused regularly, a child flow or a solution-aware design may be a better long-term structure.

Can you save or paste the action's JSON?

Cloud flows: inspect it, but do not treat it as an import format

The new designer's Code view and the classic designer's Peek code show the underlying JSON representation of an action or trigger. Microsoft states that this code cannot be edited directly to change the action.

Read Microsoft's Code view and Peek code guidance.

Code view is useful for diagnosis and understanding. It is not a supported JSON editor, action import screen or portable snippet format.

If somebody sends you raw cloud-flow JSON, ask for one of these instead:

• a flow shared with you as a co-owner;
• Send a copy;
• a non-solution .zip package;
• a solution containing the flow and its dependencies.

Desktop flows: copied actions really can be shared as text

Power Automate Desktop is different. Microsoft documents copying the actions inside a desktop subflow, sending or saving the copied text, and pasting it into another desktop flow designer.

Microsoft says the copied desktop-flow text includes the action parameters, images and UI elements. Only one subflow can be copied at a time.

See Share or export a desktop flow.

This cloud-versus-desktop difference explains why apparently convincing “paste the flow code” advice is often applied to the wrong Power Automate product.

How to duplicate or share a complete cloud flow

Copying actions is useful for a small piece of logic. It is the wrong tool for moving a complete flow.

Save As: create your own independent copy

Microsoft documents Save As for duplicating a solution-aware cloud flow.

1. Open the flow's details page.
2. Select Save As.
3. Give the new flow a clear name.
4. Select Save.

Solution context matters. If you use Save As while an unmanaged solution is open, the copy is added to that solution. Without suitable solution context, the copy may appear in My flows or the Default Solution.

Read Duplicate a solution-aware cloud flow using Save As.

Send a copy: give another person a template

Send a copy gives the recipient an independent flow based on your definition. Connections are not shared, so the recipient supplies or selects their own.

Because it creates an independent instance, you cannot later revoke access to that copied flow.

See Microsoft's Send a copy instructions.

Package: move one non-solution flow

For a one-off move of a non-solution cloud flow, export a .zip package and import it into the destination environment.

The import setup asks whether to Create as new or Update an existing flow. Microsoft labels the receiving command Import Package (Legacy) and recommends Solutions when application lifecycle management is required.

Follow Export and import a non-solution flow.

Solution: move governed flows between environments

Use a solution when a flow needs repeatable deployment through development, test and production.

Solution-aware flows can use:

• connection references;
• environment variables;
• drafts and version history;
• Power Platform pipelines;
• managed and unmanaged solution controls;
• parent and child flows kept together.

Microsoft explains these differences in Benefits of solution-aware cloud flows.

Where the Power Platform CLI fits

The Power Platform CLI is useful for solution projects and automated deployment. Its pac solution commands can export, import, pack, unpack, clone and check solutions.

It is not Microsoft's documented way to copy one action or inject an arbitrary JSON action into a cloud flow.

Use the Power Platform CLI solution commands when you are managing solution packages or an application lifecycle management pipeline—not as a replacement for the designer's action clipboard.

Does Copilot duplicate actions for you?

Copilot can help create and modify flows, but Microsoft's current guidance reviewed for this article does not document a dependable “duplicate this action and adapt it” procedure that should replace copy and paste.

If Copilot produces a similar action, treat it as newly generated logic. Check every input, expression, connection and dependency, then run a real test. Do not assume it preserved the source action exactly.

Troubleshooting copied Power Automate actions

Paste an action is missing

Check that you are right-clicking the destination +, not an empty area of the canvas. Confirm whether you are using the new or classic designer; the menu names are different.

If the flow is open through an embedded surface such as Teams or Power Apps, open its details page in the Power Automate portal. Microsoft documents some new-designer limitations in embedded surfaces.

Cross-flow paste does nothing

Treat this as a known capability/documentation mismatch. Try the classic designer if it is available, or use a whole-flow method.

Do not turn copied action JSON into a supposed workaround. Cloud-flow Code view is read-only.

Dynamic content is missing

First confirm that the step which produces the value exists before the copied action.

Microsoft also documents two reasons the dynamic content picker can hide values:

• Split On is enabled for a supporting trigger;
• the value's data type does not match the selected parameter.

Search for the value in the dynamic content picker to override its type filter. Microsoft also suggests using a Compose action, whose output can appear as type any, when the required value is hidden.

See Microsoft's dynamic content troubleshooting guidance.

The copied action asks for a connection

Select a connection you are allowed to use. A copied action definition does not grant access to somebody else's account, mailbox, SharePoint site, database or API.

For flows deployed between environments, use solution connection references rather than repeatedly repairing personal connections.

The action saves but fails during a run

Inspect the failed run and check the copied action's inputs. Pay particular attention to expressions or dynamic content that refer to an action by name, environment-specific identifiers and branches that do not exist in the new location.

Fix the reference, save and run another test. A green save message is not a substitute for a successful run with representative data.

A practical reuse policy for teams

Use the smallest supported unit that matches the job:

1. One action in one flow: copy and paste it.
2. A contained block: copy its existing Scope or Condition.
3. A reusable business operation: consider a child flow inside a solution.
4. An independent copy for another maker: Send a copy.
5. A one-off non-solution move: use a package.
6. Repeatable deployment: use a solution and pipeline.

Store documentation alongside the flow: what the block expects, which connections it needs, what values are environment-specific and how to prove it works. A clipboard entry without that context is not a reusable component; it is merely a copied card.

Frequently asked questions

What is the fastest way to duplicate a Power Automate action?

In the new cloud flow designer, right-click the action, select Copy action, right-click the destination +, and select Paste an action. Then review its dependencies and test it.

Can I copy actions from one Power Automate flow to another?

Microsoft's current documentation conflicts. Two pages describe copying between flows, while its designer comparison says the new designer does not support cross-flow or cross-tab paste. Test it in your environment; use the classic designer or a whole-flow method if it fails.

Can I copy more than one action at a time?

You can copy a supported container action such as Scope, Condition, Switch or Apply to each together with its nested actions. References to steps outside the container still need to be checked.

Can I paste raw JSON into a Power Automate cloud flow?

Microsoft does not document a native raw-JSON action import. Code view and Peek code let you inspect the underlying definition but cannot be edited directly to change the action.

Can I copy a trigger?

Do not rely on it. Microsoft's workflow creation guidance says triggers cannot be copied, although another designer page currently uses “action (or trigger)” in its steps. Recreate and verify the trigger in the destination flow.

How should I copy a complete flow?

Use Save As for your own duplicate, Send a copy for another person, a .zip package for a one-off non-solution move, or a Power Platform solution for governed deployment.

Are cloud-flow and desktop-flow clipboard formats the same?

No. Power Automate Desktop officially supports sharing copied subflow actions as text. Microsoft does not document the same text-based import mechanism for cloud-flow action JSON.

Keep your Power Automate practice current

Power Automate changes quickly, and Microsoft documentation sometimes changes faster than its comparison pages can agree with one another.

The Power Automate Builders Space brings current guidance, practical checks and flow-building discussion together in one place.

Microsoft sources used

• Explore the cloud flows designer
• Streamline workflow creation with Power Automate features
• Classic designer vs. new designer for cloud flows
• Move, delete and add options to cloud-flow actions
• Edit and duplicate a solution-aware cloud flow
• Share a cloud flow
• Export and import a non-solution flow
• Benefits of solution-aware cloud flows
• Share or export a desktop flow
• Power Platform CLI solution commands
• Troubleshoot missing dynamic content

Source boundary: this guide explains Microsoft's documented product behaviour and calls out contradictions between current Microsoft pages. Exact designer behaviour can vary by tenant, rollout state and editing surface. Test copied logic with representative data before using it in production.