Morning Email Digest Broadcast

Every morning, check unread Gmail messages, summarize the important items with AI, and send the digest through a Telegram broadcast.

The user wants an internal operational workflow that reads unread inbox items on a schedule and sends a concise Telegram summary to the team.

• Which Gmail account should be checked?
• What time should the digest be sent each morning?
• Should the digest include every unread email, only priority senders, or only emails matching a label?
• Who should receive the Telegram broadcast?
• Connect Gmail and confirm the Gmail account that should be checked.
• Review the Gmail query, for example in:inbox is:unread newer_than:1d.
• Open Broadcasting, choose the internal Telegram recipient list or team chat, then review and activate the daily schedule.
• Adjust the schedule and timezone if the team needs a different morning cutoff.

• Recurrent broadcast starts on the morning schedule
• Gmail module searches unread inbox messages, usually limited to the recent morning window
• AI_ACTION turns the unread email details into a compact team digest
• Telegram broadcast sends the digest to the selected internal recipients
• The broadcast remains reviewable so the user can choose recipients and activate it from the Broadcasting editor

Good to know

• Use create_broadcast, create_recurrence_schedule, and attach_recurrence_to_broadcast rather than a normal message-triggered flow.
• Do not create a STARTING_STEP for the broadcast flow. Link from the synthetic block id block_flow_morning_email_digest_broadcast_start.
• Use Gmail search-and-get-messages instead of search-messages when an AI summary needs sender, subject, snippet, and message details.
• Keep the broadcast as a draft and let the user choose Telegram recipients and activate the schedule in the Broadcasting editor.
• If the user wants one shared team summary, recommend a single internal Telegram group/channel recipient rather than every customer contact.

Keep in mind

• Do not use a MESSAGE or COMMAND trigger for this scheduled workflow.
• Do not send the digest before Gmail has returned message details.
• Do not use Gmail search-messages when the AI prompt needs full email details.
• Do not activate, send, or schedule the broadcast directly from AI; create a reviewable recurrent broadcast draft.
• Do not broadcast private inbox contents to broad customer audiences.