Answered

Workflow, "When an agent calls the flow", gives error

(1) Share

Report

Posted on by AS-02061149-0

When I create a new workflow in Copilot Studio, and I want to use the "When an agent calls the flow" trigger. I get the following error that says that I need to use a connection for this action before publishing. This also happens in new workflows I create but only for this specific trigger.

Schermafbeelding ...

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

Calling actions from Copilot Studio

I have the same question (0)

All responses (2)

Answers (1)

Sort by

Verified answer

SpongYe 5,905 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!

Hi @AS-02061149-0

This appears to be a connection-reference issue with the Copilot Studio agent-flow trigger.

The “When an agent calls the flow” trigger should be valid for agent flows, provided the flow also has “Respond to the agent,” is a solution flow, and is in the same environment as the agent.

I would first open the flow directly in Power Automate and check the trigger/connection status. If no missing connection is shown, try creating the flow from inside Copilot Studio using New agent flow, or use Save as in Power Automate and add the copied flow back to the agent.

If you have any questions or feedback, please let me know. Have a great day! 😊

-----------------------
SpongYe Power Platform Enthusiast [LinkedIn] | [Youtube| [My blog]

I love to share my knowledge and learn from others. If you find my posts helpful, please give them a thumbs up 👍 or mark them as a solution ✔️. You can also check out my blog [@S pongYe] for some cool solutions and insights. Feel free to connect with me on any of the platforms above. Cheers! 🍻

Was this reply helpful? Yes No
AS-02061149-0 7 on at

Like (0)

Report
Copy link

Link copied!

Hi @SpongYe,
thank you for your response
I published the flow without errors in Power Automate

The error persisted inside Copilot Studio, but when opening Copilot Studio the next day the error inside the flow disappeared.

I assume restarting Copilot Studio was the key here
Have a nice day !

Was this reply helpful? Yes No