Copilot Studio

No available option to call a Power Automate flow from Copilot Studio

(2) Share

Report

Posted on by SS-17031436-0

Hi,

I created the PA flow first, saved and tested it. It ran successfully and produced a result.

Now I want to call it from Copilot Studio. When I click Add Tool and search for Power Automate Flow, I cannot find my already built Power Automate flow. So I decided to select Get Flow — I had no other options.

After adding and configuring it, I could find my flow there.

But when I try to complete the Completion section or add relevant Topics, the output of the Power Automate flow is not recognized. After asking the agent something relevant and receiving an answer, I checked the Run History of my flow — there are no new runs. This suggests they are not connected, and Copilot is unable to run the flow.

The 'Call an Action' option does not appear for me!

Could you please assist me?

Best Ragards,

Samaneh

Categories:

Calling actions from Copilot Studio

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Suggested answer

Valantis 6,735 on at

Like
a
(2)

Report
Copy link

Link copied!

Hi @SS-17031436-0,

There are two confirmed reasons why your flow isn't showing up and why Call an Action isn't available.

1. Wrong trigger in the flow

to be available to an agent, a flow must use the trigger "When an agent calls the flow". If your flow was built with a different trigger (manual, scheduled, HTTP, etc.), Copilot Studio won't recognise it as callable. You need to modify the flow to use that specific trigger.

Steps to fix:
- Open your flow in Power Automate
- Delete the existing trigger
- Add a new trigger and search for "Copilot" or "agent"
- Select "When an agent calls the flow"
- At the end of the flow, add a "Respond to the agent" action to return outputs
- Save and publish

2. Flow must be in a solution

flows must be stored in a solution in the same Power Platform environment as your agent. Flows outside a solution won't appear in the Add Tool / Add Action picker in Copilot Studio.

To add it to a solution: go to Power Automate > Solutions > Default Solution (or your own solution) > Add existing > Cloud flows > find your flow.

Once both of these are done, go back to Copilot Studio, add the flow as a tool, and it will appear in the list and be callable from topics.

Ref: https://learn.microsoft.com/en-us/microsoft-copilot-studio/flow-modify-use-with-agent

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
Suggested answer

11manish 3,333 on at

Like
a
(0)

Report
Copy link

Link copied!

The issue is not with your Power Automate logic itself.

The actual problem is that the flow was created as a normal flow instead of an AI Agent callable flow, so Copilot Studio can discover it visually but cannot

orchestrate or execute it.

Was this reply helpful? Yes No
Suggested answer

Haque 3,653 on at

Like
a
(1)

Report
Copy link

Link copied!
Hi @SS-17031436-0,

When you don’t see your already built Power Automate flow listed in Copilot Studio’s “Add Tool” search for Power Automate Flow, it usually means:

The flow is not yet shared or published in a way that Copilot Studio can discover it.

The flow might be in a different environment or tenant than the one your Copilot Studio instance is connected to (we need to make sure flow is in Agent callable environment).

The flow might not be enabled for use as a callable tool (e.g., it needs to be a “triggered” flow with a proper HTTP or Power Platform trigger).

Permissions or licensing might restrict visibility.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
Suggested answer

Sayali-MSFT Microsoft Employee on at

Like
a
(1)

Report
Copy link

Link copied!

Hello @SS-17031436-0,

The issue occurs because the Power Automate flow is not configured with the required “When an agent calls the flow” trigger, which is mandatory for integration with Copilot Studio. As a result, the flow does not appear correctly when adding a tool, the “Call an action” option is missing, outputs are not recognized, and the agent cannot invoke the flow—evidenced by no runs in the flow history. Using “Get Flow” only imports metadata and does not enable execution.
This is expected platform behavior, not a bug, and can be resolved by recreating or modifying the flow with the correct trigger, defining return values, and ensuring it is in the same environment as the Copilot agent.

Was this reply helpful? Yes No
Suggested answer

CU19050616-2 5 on at

Like
a
(0)

Report
Copy link

Link copied!
You may try creating and triggering a Power Automate flow from a Copilot Studio Agent Topic by following the steps below:

Add a node → Add a tool → Create a flow.

You will notice the flow structure consistent with the example shown in your screenshot:

Start with “When Copilot Studio calls the flow”, to configure the required input parameters.

End with “Return values to Power Virtual Agent”, where output parameters can be defined if needed

After the flow is created, make sure to:

Rename the flow;

Test it;

Save and publish it

Important: wait a few minutes, then manually refresh Copilot Studio (press F5).

After refreshing, add a node again → Add a tool. You should then be able to find the newly created flow under the Flow category. Select it and complete the input/output parameter mapping in the Agent Topic to finish the integration.

If the above suggestion is helpful, please click “Yes”.

Thank you.

Was this reply helpful? Yes No