An urgent email reaches Telegram within the minute
The mailbox is checked often, but you only hear from it when something will not wait until tomorrow.
What the scenario looks like
Срабатывание по расписанию
Почта
Непрочитанные письма▶
Есть ли срочное▶
Модель▦
Срочное есть?▶
Сообщение в Telegram▶
Ничего срочного▶
Предупредили▶
- Execute + Data
- Data
- LLM
Mail gets read twice a day and urgent things arrive in between. Forwarding rules do not help: a rule can select by sender and by a word in the subject, and “urgent” is not described by those words.
What is inside
- Scheduled trigger — the entry.
- Unread messages fetches what has arrived since last time.
- Is anything urgent — a model answering with two fields: yes or no, and if yes, from whom and about what.
- Anything urgent? — the branch.
- The lower branch writes to Telegram; the upper one simply ends.
The quiet branch is mandatory. The check runs often, urgency is rare, and a “nothing urgent” message every half hour trains you to ignore messages from the bot — precisely what this scenario is meant to avoid.
What to set up for yourself
- What counts as urgent. The prompt gives examples and says outright: better to miss something doubtful than to wake somebody for nothing. That bias is deliberate; keep it.
- The chat on the send node.
- The frequency in the schedule settings. No more often than half-hourly on the free plan.
What to connect
A mailbox over IMAP, a Telegram bot and the Schedule target. Two connections in one scenario is exactly what a bridge between channels is: mail in, messenger out, inside a single run.