Copilot Studio Agent Flows Explained
Certified Power Apps Consultant & Host of CitizenDeveloper365
Griffin Lickfeldt’s Short focuses on adding an agent flow to a Copilot Studio agent, but its published description provides no walkthrough details.
Key insights
- The Short is titled “How to Add an Agent Flow to Agents in Copilot Studio.”
- The published description contains no setup instructions or transcript.
- Research notes say an agent flow must use the “When an agent calls the flow” trigger.
- The notes specify a “Respond to the agent” action and a synchronous response.
- The source material does not confirm the Short’s on-screen steps or interface.
Griffin Lickfeldt (Citizen Developer) published a 1-minute, 26-second YouTube Short titled “How to Add an Agent Flow to Agents in Copilot Studio.” The supplied published description contains no transcript or procedural details, so the specific clicks shown cannot be confirmed from the available material. The useful context is that an agent flow can connect an agent to defined workflow actions, but this source does not establish exactly how Lickfeldt adds one.
What's new
The Short’s subject is adding an agent flow to a Copilot Studio agent. Research notes describe an agent flow as an automation that can be added to an agent as a tool, allowing the agent to call it when appropriate. A flow can carry out predefined work; the agent interprets the request and the flow executes its configured steps.
Those notes identify key requirements for a flow intended for agent use: the “When an agent calls the flow” trigger, a “Respond to the agent” action, and a synchronous response. They also say the flow must be saved and published, and be a solution flow. These are background details, not steps verified in the Short’s published description.
Why it matters
For makers, connecting an agent to a flow offers a way to handle tasks through defined workflow logic rather than relying only on a generated response. Research notes give examples such as retrieving information, updating records, and sending notifications. The agent handles the conversational request; the flow carries out the actions configured for it.
That distinction may matter to teams that need repeatable operations. However, the supplied material does not identify a particular business scenario demonstrated in the video, nor does it provide licensing details, rollout information, or tenant availability. Admins and makers should treat the Short’s title as a topic description, not evidence of those conditions.
How it works
The background notes describe the general setup sequence, although the Short’s published description does not confirm that it shows these steps. In broad terms, a maker configures a flow for agent invocation and defines what information the flow returns.
- Use the “When an agent calls the flow” trigger and define any required inputs.
- Configure the workflow actions that perform the intended task.
- Add “Respond to the agent” so the flow returns information synchronously.
- Save and publish the flow, then add it to an agent as a tool.
The notes state that the flow needs to respond within a 100-second action limit and that asynchronous response should be turned off. These requirements are useful context, but they should not be read as a frame-by-frame account of the Short.
Limitations and open questions
The available description has no transcript, screenshots, or step-by-step explanation. It does not show where the agent-flow option appears in the interface or identify any menu labels beyond the title’s terminology. The research notes mention that the interface may use “Flow” or “Workflows,” but the exact wording in the Short cannot be verified.
No specific flow, connector, licensing requirement, or availability status is established by the supplied video material. The clip may contain visual guidance not captured in the provided description; this article does not claim to verify it.
Sources
Frequently asked questions
What does the Short explain?
Its title says it is about adding an agent flow to agents in Copilot Studio. The supplied description contains no transcript or detailed steps.
What does a flow need to be usable by an agent?
The supplied research notes specify the “When an agent calls the flow” trigger and “Respond to the agent” action, with a synchronous response. They also say the flow must be saved and published and must be a solution flow.
Does the material identify licensing or availability requirements?
No. The supplied material does not confirm licensing, rollout stage, or tenant availability.