Daily Ops Brief

Send a scheduled Telegram operations briefing that summarizes unread operational email, watchlist items, open approvals, and incident follow-ups.

The user wants a recurring internal Telegram briefing for the team, covering operational email, open issues, pending approvals, and next actions.

• What time should the daily ops brief be sent?
• Which Gmail query or label should feed the email section?
• Should the audience be contacts tagged admin/ops, a team chat, or selected internal contacts?
• Which standing watchlist items should be included every day?
• Connect Gmail and confirm which mailbox or label should feed the brief.
• Review opsBriefEmailQuery, for example in:inbox is:unread newer_than:1d.
• Set opsBriefWatchlist to the team's standing checks, such as open incidents, pending approvals, failed jobs, VIP customers, or billing exceptions.
• Open Broadcasting, choose the internal admin/ops recipient audience, and activate the recurrence after review.

• Recurrent broadcast starts on the morning schedule
• Gmail module fetches unread or labeled operational messages
• AI_ACTION combines the email details with configured watchlist notes
• The brief highlights urgent items, incidents, approvals, owners, and next actions
• Telegram broadcast sends the summary to the internal audience selected in Broadcasting
• Audience should usually be contacts tagged admin/ops or a specific internal team recipient list

Good to know

• Use create_broadcast, create_recurrence_schedule, and attach_recurrence_to_broadcast for recurring daily briefs.
• Do not create a normal MESSAGE trigger for a scheduled daily brief.
• Use Gmail search-and-get-messages when the AI prompt needs sender, subject, snippet, and message details.
• Keep the broadcast as a reviewable draft. The user should choose the internal audience and activate the schedule in the Broadcasting editor.
• Prefer a tag or segment such as ops/admin for the audience. Use hardcoded Telegram IDs only as a temporary migration path.
• If approval or incident templates are also installed, mention their open status variables in opsBriefWatchlist until a direct query module/API exists.

Keep in mind

• Do not activate or send the broadcast directly from AI actions.
• Do not send private operational email to customer audiences.
• Do not use Gmail search-messages when the AI prompt needs full message details.
• Do not pretend to query incidents, approvals, or revenue unless those integrations or variables exist.