Meeting Preparation

Daily Sales Meeting Prep Digest — Outlook + Power Automate

A weekday morning Power Automate run sends a concise digest of sales meetings, attendees, agenda and approved CRM links without Zapier or Claude API.

Automated
Intermediate
Weekdays at 07:30 local time (adjust to seller's timezone)
Microsoft 365 Outlook + Power Automate + Teams; optional Dynamics 365

What this scheduled task delivers

A scheduled morning digest is simpler than ten separate 90-minute AI requests. Power Automate reads approved Outlook calendar entries each weekday and sends a single structured agenda with links and questions to the seller's private Teams chat. This is a clock-started task, NOT a business-event trigger. It never guesses account pain, news, or stakeholder intent.

Process and start condition

Weekday recurrence at 07:30 local timezone → Outlook calendar view for today → include Sales-category meetings → format agenda/attendees and optionally verified CRM link → post one internal Teams message → AE adds research manually.

Before you begin

Microsoft 365 Outlook calendar and Power Automate permissions, Teams connection with right to send to seller's personal chat. The seller must mark eligible events with Outlook category Sales. Optional Dynamics 365/Dataverse connector requires approved licensing and a verified CRM Deal ID saved in the event body. Configure your own local timezone explicitly (example America/Chicago only if that's your actual timezone).

Prepare your inputs

For each Outlook event: Event ID, Start Time, Subject, Attendee addresses, agenda text, Category=Sales, optional CRM Deal Link manually supplied in the meeting body. Fictional Meeting EV-88, 09:30, Northstar discovery, attendees avery@northstar.example, agenda 'qualify rollout scope', CRM link blank. No match → 'CRM context not linked'.

Build the scheduled flow

  1. Power Automate → Create → Scheduled cloud flow (Recurrence); Frequency=Week, Interval=1, On these days=Monday–Friday, At=07:30 in the SELLER'S configured timezone. Name 'Sales Morning Prep'. Do not use an ambiguous UTC hour.
  2. Office 365 Outlook → Get calendar view of events (V3): select the owned Calendar ID; Start Time=today 00:00 local converted to UTC; End Time=tomorrow 00:00 local converted to UTC. Use ISO UTC timestamps supported by the action, not plain date-only values.
  3. Filter returned events: Category includes Sales, has a valid Start Time, and isn't canceled; deduplicate Event ID across recurrences. Use Apply to each to format Start local time, Subject, invitees, saved agenda and (if present) the explicitly provided CRM Deal link.
  4. Compose one digest with up to ten sales events (or paginated blocks), plus 'Prep questions: meeting objective? desired decision? last committed next step?' Mark missing agenda/CRM link as missing rather than inventing an account brief. If there are no eligible meetings, stop without a noisy message.
  5. Microsoft Teams → Post message in a chat or channel to the seller's authorized personal chat with the composed digest. Inspect a sample run on an approved test calendar; if Teams posting fails, retry only the message after checking the run's date/event IDs. Seller clicks CRM links and researches unsupported details.

Test or review

Paper walkthrough: EV-88 appears once at 09:30 with attendees and agenda; missing CRM link is clearly flagged. Test daylight saving changes, canceled event, internal non-Sales events, more than ten meetings, no meetings, duplicate retry and Teams permissions. No scheduled task was activated. Documentation-verified; execution untested.

Expected output

Fictional 07:30 digest: '09:30 Northstar discovery | Objective: rollout scope | Attendee: Avery | CRM: not linked | Prep question: who owns rollout decisions?'

Maintain and troubleshoot

No message: inspect Recurrence timezone, run history and category tag. Events missing: check Calendar ID and UTC window. Wrong timezone: test around daylight savings. Pause by turning off the cloud flow; don't ask an unsupported LLM to invent the briefing.

Official documentation

Fictional examples. Customer is responsible for enabling integrations and approving communications.