Response of Copilot Agent from Power Automate flow

(2) Share

Report

Posted on by CU25090116-0

Trying to access response from Copilot agent in Power Automate flow, but not able to get anything from body('Execute_Copilot')?['message'] in Power Automate. Is there a way to get it in Power Automate flow?

Read somewhere - call to Copilot agent is asynchronous, is there a connector from Power Automate to Copilot agent to get the response?

Categories:

Building flows

I have the same question (2)

All responses (4)

Answers (0)

Suggested answer

Michael E. Gernaey 53,569 Super User 2025 Season 2 on at

Like (0)

Report

Hi @CU25090116-0

There is no perfect way to do it as the execute does not give you anything but a pretty much useless conversation ID.

My suggestion is to create a secondary Flow that the Agent calls when it's done doing whatever you wanted it to do and continue processing there or simply use an in Agent Flow to continue the work.

There are other things, like having the Agent create a record somewhere and a flow trigger, or send an email etc.. for me thats all less as efficient as either just using an in Agent Flow and or Trigger in the Agent to do all the work, or have that agent call a secondary Flow to continue the work.

If these suggestions help resolve your issue, Please consider Marking the answer as such and also maybe a like.

Thank you!
Sincerely, Michael Gernaey

Was this reply helpful? Yes No
ProPosia 54 on at

Like (0)

Report

Hello,

Reference: https://learn.microsoft.com/en-us/connectors/microsoftcopilotstudio/
https://learn.microsoft.com/en-us/microsoft-copilot-studio/flow-agent?utm_source=chatgpt.com
https://learn.microsoft.com/en-us/dynamics365/customer-service/develop/bring-your-own-channel

Execute Copilot doesn’t return the agent’s text—it only returns a ConversationId. So body('Execute_Copilot')?['message'] will be empty by design. Use body('Execute_Copilot')?['ConversationId'].

Recommended (supported): Agent → Flow
Have your Copilot agent call a Power Automate flow and Respond to the agent from the flow. Make sure Asynchronous response = Off so the agent waits and shows the flow’s output immediately.

Advanced (if you must Flow → Agent):
Wrap the agent with Direct Line (small Azure Function/Logic App) that starts the turn, polls activities, then returns the final message to your flow via a Custom Connector.
Also @CU25090116-0, The old “Execute Copilot and wait” actions that returned responses/lastResponse are deprecated. Don’t rely on them.

I hope this helps.

Was this reply helpful? Yes No
Inogic 1,135 Super User 2025 Season 2 on at

Like (1)

Report
Hi,

Please follow this steps to achieve this.

Step 1:

In Copilot Studio, create a new topic. Within that topic, add an action to call a Power Automate flow by selecting New Agent flow.

Step 2:
New Agent Flow i.e. Power Automate Flow will look like this

The trigger must be “When an agent calls the flow”.

The last step in the flow should be “Respond to the agent”.

Any logic or processing steps can be added between the trigger and the response.

The trigger receives input from Copilot, and the response is sent back to the agent.

Hope this helps to resolve the issue .

Thanks!

Inogic

Was this reply helpful? Yes No
mdittler 7 on at

Like (0)

Report

Generally speaking, these solutions aren't very helpful. In our use case, we have a copilot studio agent that brings together a lot of different data sources and provides information in a specific format. When performing an action, they need to start the conversation off with that specific query every time. It would be great to be able to submit a prompt with dynamic fields to the agent, then post the response on a teams board or something similar to get the activity started. It would only be helpful in our application if the prompt could be triggered by a new planner task or when a form is submitted or something. It could also be helpful for periodic reviews of certain document repositories. to make sure things are up to date or there aren't new risks.

Was this reply helpful? Yes No