A weekday morning Power Automate run sends a concise digest of sales meetings, attendees, agenda and approved CRM links without Zapier or Claude API.
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.
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.
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).
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'.
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.
Fictional 07:30 digest: '09:30 Northstar discovery | Objective: rollout scope | Attendee: Avery | CRM: not linked | Prep question: who owns rollout decisions?'
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.
Fictional examples. Customer is responsible for enabling integrations and approving communications.