In the overview of runs in Power Automate, you can add extra columns these days.
These columns can contain information from the inputs that the trigger receives.

For example:

• the input fields of a manual flow
• request information of a HTTP trigger
• item information of a SharePoint item triggering the flow.

That is superuseful because it allows people to have a quick overview of what a flow run was all about. Without opening the Flow run

Examples

Example of HTTP Request trigger input:

Example of manual input:

Implementation

We could add it to the CLI on the flow run list and flow run get commands, to make it easier to view this data in one overview as well.

What the UI seems to do is fire an extra HTTP request for every flow run:

HTTP GET https://prod-173.westeurope.logic.azure.com/workflows/<flowId>/runs/<runId>/contents/TriggerOutputs?api-version=2016-06-01&se=2023-06-22T14%3A00%3A00.0000000Z&sp=%2Fruns%2F<somevalue>%2Fcontents%2FTriggerOutputs%2Fread&sv=1.0&sig=<sigValue>

Response:

{
    "headers": {
        //...etc
        "Content-Type": "application/json"
    },
    "body": {
        "text": "text1",
        "text_1": "text2",
        "boolean": true,
        "email": "[email protected]",
        "date": "2023-06-22"
    }
}

As this is quite costly when listing numerous items, I'd suggest we add this using a flag, for flow run list and flow run get:

Option

Remarks

Note: When using --withTrigger, extra requests will get fired for each retrieved flow run. This has impact on the time the command takes to run.