Event-driven and multi-path flows
1. Event-driven and multi-path flows
So far, your flows have waited for an agent to call them. But some work should start on its own, like reviewing every AI news article the moment it's published. That's a job for an event-driven flow.2. Triggers you configure but don't fire
These flows start on an event, like a new RSS item or an MSN Weather change. On this learning tenant, though, automated triggers are configure-only: you build and connect the whole flow, but no live events reach it, so nothing fires. On a real tenant, the same flow would run each time a new item arrives.3. A human in the loop
The second idea is human review. Before a flow does something consequential, you often want a person to sign off. Under AI capabilities, Human review has a step called Request information: it pauses the flow, asks the reviewer to approve, and waits for a Yes or No.4. Add the RSS trigger
Let's build the AI Article Review flow. Start a new Agent flows workflow from the arrow beside New workflow, then in Add a trigger search for RSS and point it at The Verge's AI feed.5. Summarize the article
Click the plus, choose Run a prompt under AI capabilities, and pick the ready-made AI Summarize prompt. Feed it the feed item's summary. That short blurb is what your reviewer reads.6. Ask a person to approve
Add Request information next, from AI capabilities then Human review, asking the reviewer whether to share the article. The flow stops here and hands the decision to a person.7. Add the condition on the answer
Click the plus, then Built-in tools, Control, and Condition. Set it to check the reviewer's answer. That answer splits the flow into two routes.8. Route the True branch
On the True branch, add the Office 365 Outlook action Draft an email message. Drafting instead of sending means nothing goes out by accident. Teams isn't available here, so Outlook stands in. The first time you use a connector, sign in and pick your account.9. Route the False branch
On the False branch, add Terminate from Built-in tools and Control, and change its status from Failed to Cancelled. A rejected article isn't an error, and the run should say so.10. Save and review the structure
Click Save draft, and since the trigger can't fire here, you're checking the shape, not a live run: feed item in, summary, human approval, a condition, and two routes out.11. Insert a step in the right place
You can also add a review step to a flow that already sends something out. Use the plus directly above the output action, not the one below it. Then read the canvas top to bottom: the step that writes the content, then Request information, then the send. A review after the send can't stop anything.12. Let's practice!
Now it's your turn to build an event-driven review flow, then add a review step to a short flow that emails straight out.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.