What this automates
The highest-value 30 minutes of manual Copilot use is pre-meeting prep: who am I meeting, what did we last discuss, what’s open, what should I ask. This blueprint removes the “manual”: a scheduled workflow does that prep for every meeting on today’s calendar and emails you the stack before you’ve had coffee.
This is the canonical first workflow because it touches no shared systems, sends only to you, and demonstrates the agent node’s judgment visibly — every brief is different because every meeting is different. It’s the demo that makes executives stop asking “what’s an agentic workflow?”
The design
| Step | Node | What it does |
|---|---|---|
| 1 | Schedule trigger | Weekdays, 7:30 AM, your timezone |
| 2 | Outlook — get calendar view | Pulls today’s events; filter out all-day events and appointments with no other attendees |
| 3 | Loop — for each meeting | Iterates the filtered list |
| 4 | Agent node (the brain) | Inline agent with Work IQ on builds the brief — see instructions below |
| 5 | Compose | Assembles the per-meeting briefs into one HTML digest |
| 6 | Send | Emails the digest to you; optionally posts an adaptive card to your Teams chat with yourself |
The agent node, configured
Create it inline in the workflow designer (Add panel → Agent). Choose a more capable model — this is multi-step reasoning, not classification. Turn Work IQ ON — that’s what lets the agent see your recent mail, Teams threads, and files with these attendees. No tools needed; this agent only reads and reasons. Output: text response.
Instructions for the node (paste, then adjust the bracketed parts):
You prepare a pre-meeting brief. The meeting: subject, time, attendees and
body are below as dynamic content.
Using recent emails, Teams messages, meetings, and files involving these
attendees, produce a brief in EXACTLY this format, max 180 words:
WHO: one line per external-to-my-team attendee — role and what they own.
LAST CONTACT: the 2-3 most recent meaningful exchanges with these people —
decisions, asks, commitments. Cite the source (email subject / channel /
meeting name).
OPEN ITEMS: commitments either side made and hasn't closed. Mark mine with ▶.
WALK-IN QUESTIONS: 3 questions these attendees are likely to ask me, based
on the open items.
Rules: facts only, every claim traceable to a real artifact. If context is
thin (new contact, first meeting), say "Thin file — first substantive
meeting" and give WHO only. Never pad.
Meeting subject: [Subject token]
Attendees: [RequiredAttendees token]
Body: [Body token]The “thin file” rule matters more than it looks: without it, the agent pads first-meetings with LinkedIn-style generalities, and your trust in the whole digest dies the first time you read one.
Build it (about an hour)
- In Copilot Studio, go to Flows → New workflow. Set the schedule trigger: weekdays, 7:30 AM.
- Add the Outlook Get calendar view action for today’s window. Add a condition to skip events where you’re the only attendee and all-day events.
- Add the loop over remaining events. Inside it, add the Agent node from the Add panel; configure as above, feeding the subject/attendees/body tokens.
- After the loop, compose the digest: meeting time + subject as headers, the agent’s brief under each.
- Add the Send an email action to yourself. Test with node-level testing on the agent node first — feed it one real meeting and read the output before wiring the rest.
- Run it manually once (today’s calendar), fix what reads wrong, then publish and let the schedule take over.
Cost and governance notes
- Credits: each workflow action consumes Copilot Studio capacity, and the agent node is the expensive step — budget roughly per-meeting-per-day. Use the agent usage estimator before rolling this to a team; for one person it’s pocket change, for 500 sellers it’s a real line item.
- Permissions: the agent node runs as the triggering user — your briefs are built from what you can see, nobody else’s mail. Rolling it out to a team means each user triggers their own run; nobody inherits anyone’s access.
- The two-minute rule: long calendars can push runtime; if your org’s calendars are heavy, enable asynchronous responses for the flow so it isn’t killed mid-loop.
Variants worth building once this works
- Sales edition: add a Dynamics/CRM lookup step before the agent node and feed account context into the instructions (the pattern Microsoft documents for opportunity research with Researcher).
- Exec edition: change delivery to a single adaptive card in Teams at 7:55, briefs sorted by meeting importance rather than time.
- Cowork alternative: a single person can approximate this with a Cowork scheduled prompt + the Meetings skill — no Copilot Studio needed. The workflow version wins when you want it standardized, governed, and rolled out beyond yourself.