Copilot Studio Power Automate Flow Returns No Output: Fix

When you call a Power Automate flow from Copilot Studio, the expected response may be blank or missing. This usually happens when the flow finishes without sending data back to the copilot topic. The root cause is often a missing or incorrectly formatted output variable in the flow. This article explains why the output is empty and provides a step-by-step fix to ensure the flow returns data correctly.

Why a Power Automate Flow Returns No Output in Copilot Studio

Copilot Studio sends a request to a Power Automate flow when a topic triggers it. The flow runs and should return a response to the copilot. If the flow does not include a Response action, the copilot receives nothing. The flow finishes successfully but the output variable is empty. This is the most common cause.

Another cause is a mismatch between the output variable name in the flow and the name referenced in the Copilot Studio topic. Copilot Studio expects a specific JSON key. If the flow returns a different key, the copilot cannot read the data. The output appears blank.

A third cause is the flow running in the wrong context. Copilot Studio flows must use the Microsoft Dataverse connector or the Power Automate connector. Flows that use other connectors may not return data correctly. Also, the flow must be shared with the copilot creator or the end user.

Steps to Fix a Power Automate Flow That Returns No Output

Follow these steps to identify and fix the missing output. You need edit access to both Copilot Studio and Power Automate.

1. Open the copilot topic that calls the flow
   In Copilot Studio, go to Topics and select the topic that triggers the flow. Find the Flow action node that calls the Power Automate flow. Click the node to see its properties.
2. Check the output variable name
   In the Flow action properties, look for the Output variable field. Note the exact variable name. Copilot Studio uses this name to read the response. If this field is blank, the copilot will not capture any output.
3. Open the Power Automate flow
   In Power Automate, find the flow used by the copilot. Open the flow in edit mode. Look at the last action in the flow. It must be a Response action. If the flow ends with any other action, the output will be lost.
4. Add a Response action
   If the flow does not have a Response action, add one. Click the plus sign between the last action and the end of the flow. Search for Response and select it. The Response action appears as the final step.
5. Set the response body to a JSON object
   In the Response action, set the Body field to a JSON object. Use the same variable name from step 2. For example, if the output variable is named “flowOutput”, set the body to: { "flowOutput": "@outputs('PreviousActionName')" }. Replace PreviousActionName with the name of the action that produces the data.
6. Save and test the flow
   Save the flow in Power Automate. Return to Copilot Studio. Open the Test pane and run the topic that calls the flow. In the test pane, click Show diagnostics to see the raw response. Look for the output variable in the response JSON. If the variable appears with data, the fix works.
7. Verify the flow is shared
   In Power Automate, go to the flow details page. Click Share and confirm that the copilot creator or the end user has access. If the flow is not shared, the copilot cannot trigger it.

If Copilot Studio Still Shows No Output After the Main Fix

Sometimes the basic fix does not resolve the issue. Below are other failure patterns and their specific solutions.

Flow Returns Data but Copilot Shows Blank

This happens when the JSON structure does not match what Copilot Studio expects. Open the Response action and confirm the JSON key matches the output variable name exactly. Use lowercase letters and no spaces. For example, if the variable is “orderNumber”, the JSON key must be “orderNumber” not “OrderNumber”.

Flow Runs but Fails with a 400 or 500 Error

Check the flow run history in Power Automate. Open the flow and select Run history. Look for failed runs. Common errors include missing permissions, invalid input parameters, or connector limits. Fix the error in the flow and run the test again.

Flow Does Not Trigger at All

If the flow never runs, the trigger might be misconfigured. In Copilot Studio, open the Flow action node and verify the flow is selected correctly. Click the refresh button to reload the list of available flows. Also, ensure the flow is set to trigger from a copilot. In Power Automate, the trigger should be “When a copilot calls a flow” or similar.

Output Variable Shows Null

If the response contains the variable but its value is null, the previous action in the flow did not produce data. Open the flow and check the action that generates the data. Verify that the action returns a value. For example, if you use a Get item action, confirm the item exists and the action is configured to return all fields.

Copilot Studio Flow Output: Common Settings Compared

Item	Correct Configuration	Incorrect Configuration
Response action present	Last action is Response	Last action is Compose or Terminate
Response body format	Valid JSON with matching key	Plain text or missing key
Output variable name in Copilot Studio	Matches JSON key exactly	Different case or spelling
Flow sharing	Shared with copilot creator	Private or shared with wrong user
Flow trigger	When a copilot calls a flow	Manual or scheduled trigger

After making these changes, test the flow again in Copilot Studio. Use the diagnostics panel to confirm the output variable contains the expected data. The blank response should now show the correct information from the flow.

If the flow still returns no output, review the flow run history for any errors. Check the input parameters passed from Copilot Studio. Ensure the flow uses the Microsoft Dataverse connector or the Power Automate connector. Avoid using third-party connectors that may not support the copilot integration. You can also create a simple test flow that returns a static JSON value to isolate whether the issue is in the flow logic or the integration itself.