web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Automate / Enhancement Request: I...
Power Automate
Unanswered

Enhancement Request: Improve Output Reuse and Debugging Experience in Power Automate

(1) ShareShare
ReportReport
Posted on by 2

Summary

 

Power Automate is powerful but unnecessarily difficult to use when building or debugging flows due to friction around accessing and reusing action outputs. A streamlined way to copy outputs from one action and insert them into subsequent actions would significantly improve developer productivity and reduce frustration.

 
 

Problem Description

 

Today, when building or debugging flows, it is common to:

 

  1. Run a flow

  2. Open a specific action card

  3. Navigate to the Outputs tab (last tab)

  4. Manually copy output text or JSON

  5. Paste it into the next action and guess at the correct syntax


  6.  
 

This workflow is slow, error-prone, and unintuitive—especially for complex expressions, JSON parsing, or dynamic content references.

 

As a result, users (including experienced engineers) can spend hours debugging syntax issues that stem from small mistakes when manually copying or reformatting outputs.

 
 

Key Pain Points

 

  • No easy way to reuse outputs from one step directly in the next step

  • Output copying requires multiple clicks and manual formatting

  • High likelihood of syntax errors when pasting JSON or expressions

  • Debugging experience is disconnected from flow authoring

  • The new AI helper is helpful but:

    • Only works with a limited subset of cards

    • Cannot consistently help with complex expressions or output transformations


    •  


  •  
 
 

Proposed Enhancements

 

1. “Copy Output as Expression” Action

 

Add a one-click option in the Outputs tab of an action:

 

  • Copy as Expression

  • Copy as JSON

  • Copy as Dynamic Content Reference


  •  
 

This would generate correct, ready-to-use syntax for downstream actions.

 

2. Output-to-Input Binding

 

Allow users to:

 

  • Right-click an output value

  • Select “Use in next action”

  • Automatically insert it into a selected field in another card


  •  
 

3. Inline Output Picker

 

When editing an input field:

 

  • Show recent outputs from previous steps

  • Allow search/filter by action name and property

  • Insert them without navigating away from the card


  •  
 

4. Expand AI Helper Coverage

 

  • Enable the AI helper across all action types

  • Allow it to understand flow history outputs

  • Let it suggest fixed expressions based on actual runtime outputs


  •  
 
 

Expected Benefits

 

  • Dramatically reduced debugging time

  • Fewer syntax and formatting errors

  • Improved developer confidence and adoption

  • More approachable experience for both new and advanced users

  • Stronger parity with modern low-code/no-code tooling expectations


  •  
 
 

Conclusion

 

Power Automate is extremely capable, but the current output reuse and debugging workflow creates unnecessary friction. Small UX enhancements—especially around copying and reusing outputs—would have an outsized positive impact on productivity and user satisfaction.

 

Thank you for considering this feedback.

 
 

If you want, I can:

 

  • Rewrite this to sound more concise or more technical

  • Tailor it specifically for the Power Automate Ideas forum format

  • Adjust tone to be more executive, developer-centric, or support-focused

  • Turn it into a short version + long version combo


  •  
 

Just tell me how you plan to submit it.

Categories:
I have the same question (0)
  • lbendlin Profile Picture
    8,677 Super User 2026 Season 1 on at
    Please vote for an existing idea or raise a new one here https://ideas.powerautomate.com/d365community/forum/086dd68e-597f-ec11-8d21-0022482e8f9f
  • Sunil Kumar Pashikanti Profile Picture
    1,681 Moderator on at
     

    This would be best submitted to the Power Automate Ideas site so it can be voted on and tracked by the product team.

    A concise Ideas‑portal version, with an optional longer/expanded version for detail, would be ideal. A developer / enterprise‑centric tone would probably resonate most, since this impacts complex flows and debugging scenarios significantly.

    Happy to proceed that way.

     

    @Sunil Kumar Pashikanti

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the March Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Haque Profile Picture

Haque 607

#2
Valantis Profile Picture

Valantis 456

#3
11manish Profile Picture

11manish 352

Last 30 days Overall leaderboard