COPILOT STUDIO — PROJECT 3🟡 INTERMEDIATE
FlowConnect-Agent — leave requests via Power Automate actions and Adaptive Card approvals. Static reference showing the confirm-before-act pattern and cost-tiered action design.
Leave Request Agent
How many leave days do I have left?
Agent Flow · lookup You have 8 casual leave days remaining this year.
I want to take leave from July 20 to July 22 for a family event
Cloud Flow Action · pending confirmation I'll submit a leave request: July 20–22 (3 days), reason: family event.
Confirm and submit to your manager? Confirm
Cloud Flow Action · executed Submitted! Here's the approval card sent to your manager:
🗓 Leave Approval Request
Priya S. · Jul 20–22 · Family event
Approve
Reject
Type a message…

Actions on this agent

Get My Leave BalanceAgent Flow
Create Leave RequestCloud Flow
Notify Approval OutcomeCloud Flow

Credit cost this session

Balance lookup~5 cr
Leave request + confirm~7 cr
Total~12 cr

Design note

Balance lookup deliberately uses a cheap, deterministic agent flow instead of a full reasoning action — high-frequency questions stay inexpensive by design.
What this shows: the agent never creates a record without an explicit confirmation step first. Routine lookups use a lightweight agent flow (cheaper, deterministic) while the actual state-changing request uses a full cloud flow action with an Adaptive Card human-approval loop — a deliberate cost and safety tiering, not an accident of what was easiest to build.