I'm facing a challenge with a Copilot Studio flow and would appreciate any insights.
My Goal:
I have a cloud flow that triggers when a new .docx file is created in a SharePoint library. The goal is to:
-
Extract the plain text content from the
.docxfile. -
Send this text to a specific, custom-built Copilot Studio agent with a prompt to generate a business plan.
-
Take the final text response from the Copilot agent.
-
Save that response as a new file in another SharePoint library.
What I've Accomplished:
The text extraction from the .docx file is working perfectly. I've built a robust process using OneDrive to unzip the file and an xpath() expression on the document.xml file to get the plain text. This part is 100% successful.
The Problem:
The issue is with the Execute Copilot action from the "Microsoft Copilot Studio" connector. I am required to use this specific agent, so I must use this action.
When I run the flow, I've checked the run history and confirmed that this action is asynchronous.
-
The raw output of the action shows a
statusCode: 202(Accepted). -
The
bodyof the output only contains aconversationID. It does not contain the generated text from the agent.
What I've Tried:
-
Inspecting Outputs: I've checked every available dynamic content "pill" from the
Execute Copilotaction (Body,Copilot response, etc.). At runtime, they all resolve to an object containing just theconversationID, not the final text response. -
Adding a
Delay: I tried adding aDelayof up to 2 minutes after theExecute Copilotaction, hoping the output variables would eventually be populated with the final text. This did not work; the output was still just theconversationID. -
Calling the action again: I tried calling
Execute Copilota second time, feeding theconversationIDfrom the first call into theConversation IDinput parameter. The second call also only returned a new ID without the response from the first call's prompt. -
Looking for another action: I've confirmed that the "Microsoft Copilot Studio" connector in my environment only has one action:
Execute Copilot. There is no corresponding "Get Copilot response" or "Check status" action to retrieve the result using theconversationID.
My Question:
How can I retrieve the final text response from a Copilot Studio agent within the same Power Automate flow when the Execute Copilot action behaves asynchronously and the connector does not provide a corresponding action to get the result?
It feels like a "fire-and-forget" action with no native way to retrieve the response, which makes it very difficult to use for this kind of end-to-end automation. Is there a known pattern for this specific connector that I am missing?
Any help or insight would be greatly appreciated. Thank you!

Report
All responses (
Answers (