◇ Could this help me?
Yes for the scheduling, with the access scope treated more carefully than the video does. The underlying shift is real and worth adopting: a recurring job described in plain language replaces what used to be hours of connecting services together, and a morning digest of mail needing replies plus the day's meetings is a genuinely useful first one because it is read-only and easy to sanity check. The part to add is scoping, because the same convenience that makes this fast also makes it easy to grant an unattended task far more access than the job requires. General practice, with the specific guardrail that a scheduled task reading an inbox is consuming content written by other people with nobody watching, so it should produce a summary for review rather than send anything on your behalf.
Help me set up a recurring morning briefing, and be strict about access. I want a scheduled task that reads my mail, identifies messages that genuinely need a reply, checks my calendar for the day, and delivers one short digest at a set time. Before setting it up, tell me the minimum permissions it needs for each source, and set it up so it can read but cannot send, reply, or delete anything. The output should be a summary with recommendations and nothing else: no actions taken on my behalf. Then tell me what could go wrong with an unattended task that reads an inbox, including what happens if a message contains instructions aimed at you, and how the setup should handle that.