Your first agent flow
1. Your first agent flow
Your agent can recognize what someone means and route it to the right topic. But it can't act on a request yet, like drafting a reply to a customer. For that, you need a flow.2. A topic talks, a flow acts
A topic is conversational: it listens for intent and responds. A flow is procedural: it runs the same fixed steps every time, so it's the right tool for work you repeat step for step.3. The four-part backbone
Almost every basic flow has the same four parts: a trigger starts it, an input arrives, an AI step generates content, and a final step hands it back.4. Find Agent flows
Flows don't live inside the agent, so let's start by clicking Workflows in the left rail. It works the same way as with agents: don't click the blue New workflow button. Click the small arrow to its right and pick Agent flows, not the "uses credits" group above it.5. It opens in a new tab
Agent flows open in a new tab with its own rail: Home, Agents, Flows, and Tools. Skip any welcome tour or consent card, because accepting one mid-create sends you back to Home.6. Set the trigger
Every flow needs to know what starts it. On Add a trigger, search Copilot and pick "when an agent calls the flow". With any other trigger, your flow won't publish.7. Add an input
Collecting the input isn't a separate step. On the trigger node, click Add an input, choose Text, and name it Inquiry. That's how the agent passes in the customer's message.8. Run a prompt
Click the plus below the trigger and, under AI capabilities, choose Run a prompt. Set up the one-time Dataverse connection it asks for, then pick the ready-made AI Reply from the Prompt dropdown. In Input Text, press slash, choose Insert dynamic content, and pick Inquiry.9. Respond to the agent
Finish with Respond to the agent, from the same menu, and add an output to carry the drafted reply back for review. That wires the backbone: trigger, collect, generate, and present.10. Save your draft
Click Save draft, and a banner confirms it. Rename it from Untitled under Details, and if an edit goes wrong, Version history restores an earlier save.11. Publish before you test
Saving isn't enough, because Test stays grayed out until you publish. Publishing also validates the flow, and the Flow checker names any missing step or field. Once it's live, test it with a rough inquiry, such as "do you ship to Canada?", and read the draft in the run's outputs. Would you actually send it?12. Let the agent call your flow
In your agent, open Tools, choose Add a tool, then Workflows, and pick your flow. Describe the tool and say when to use it, or the agent may answer on its own. Ask about shipping, and the activity map shows the flow ran.13. Let's practice!
It's your turn to build a draft-response flow from trigger to reply, and publish it.Create Your Free Account
or
By continuing, you accept our Terms of Use, our Privacy Policy and that your data is stored in the USA.