A morning email about what landed overnight
One email instead of forty: what arrived, from whom, and which of it wants an answer.
What the scenario looks like
- Execute + Data
- Data
- LLM
The morning starts with forty emails, three of which matter. Sorting them takes twenty minutes and happens on a fresh head — which is to say, at the expense of the time that was supposed to go into work.
What is inside
- Scheduled trigger — the entry.
- Mail — the connection node. Every mail step takes its access from it: one place instead of two.
- Unread messages fetches what has piled up.
- Morning digest — the model. It groups by topic, separates anything urgent and folds newsletters into a single line with a count.
- Digest email sends the result to you.
The “mark as read” flag on the fetch node is off: a digest should not change the state of the mailbox. Turn it on only if the digest replaces the inbox for you, or messages become read before you have seen them.
What to set up for yourself
- The digest prompt. It currently groups by topic. Your order may differ: customers first, then money, then everything else.
- The recipient on the send node: replace
REPLACE_MEwith your own address. - How many messages (
max_count). Thirty usually covers a night; a Monday after a weekend, not so much. - Where it goes. The digest can land in Telegram instead: swap the last node, the rest is unchanged.
What to connect
A mailbox. In settings, add a connection: the IMAP server address, the login and an app password — a normal mail password will not do with most providers. Then enable the Schedule target on the Publish tab and set it for the morning.