your morning brief: today's meetings and the mail behind them

the routine

connect your work gmail and google calendar in Connected apps. allow this bot to read each. change the time and calendar name in the message to fit your morning.

every weekday at 8:15, give me a brief for today in this chat. use my work gmail and work calendar only.

start with today’s date and time zone. find today’s meetings and read recent email threads involving their attendees or project names. only join a thread to a meeting when the connection is clear.

list my first meeting, what i need to bring, and any request due today. for each item give the meeting time, sender or event title, and a source link when available. separate confirmed requests from suggested prep. if two sources disagree, show both. finish with anything you could not check.

keep it short. do not label mail, create drafts, reply, or change events.

when

weekday mornings at 8:15; confirm the routine’s time zone with the bot

needs

work gmail and google calendar connected with read-only access

what comes back looks like this (an example, not a real inbox)

today’s brief for sam, 8:15 local time

first: 9:30, acme handover with priya.
confirmed prep: priya’s latest thread asks for the revised delivery note. source: email thread “acme handover”.
decision due today: jo needs a yes on the workshop venue before noon. source: email “venue hold”.
suggested prep: read your delivery note before the handover.
not checked: the attachment mentioned in priya’s message was unavailable. do not assume it matches your copy.

join the context, not every message

a useful brief answers “what do i need before my first conversation?” tell the bot which calendar belongs to work and which inbox carries the supporting mail. gmail can fetch messages and whole threads; google calendar has a find-event action. these are enough to build a brief without writing into either app.⁴⁵

ask for the reason behind each suggested task. an attendee’s name appearing in a thread does not prove that thread is meeting prep. leave loose matches out, or put them under questions.

keep confirmed requests separate from guesses

a deadline stated in an email is different from the bot’s suggestion to prepare a document. keeping those apart lets you decide what matters without treating a guess as a commitment. if a meeting title is vague, add the project name to the routine.

for a deeper look at one call, use the meeting prep brief. the gmail connection guide explains the mail access; the google calendar guide covers the calendar side.

a brief can be incomplete

it cannot know about a call arranged outside the connected calendar or a deadline someone only told you aloud. ask it to name unavailable sources instead of filling the gaps. check the original event before leaving for a meeting.

on your computer, the morning run needs dusk bot open and the machine awake. a run missed by less than 12 hours runs once when you return; older runs are skipped. dusk cloud runs routines on time if the brief must be ready before you open your laptop.

the guard rails

• keep both app connections read-only for this bot; the brief needs no edits
• name the work accounts so personal appointments and mail stay outside the brief
• require a source for each deadline and mark suggested prep as a suggestion
• leave sensitive message text out of the brief when an event title and link are enough