The flow
Starts it 3Logic 7Service 6
The steps in the order they run, from what starts it.
- 1Trigger weekly at SundaySchedule triggerStarts it
- 2Trigger daily at midnightSchedule triggerStarts it
- 3Trigger dailySchedule triggerStarts it
- 4Get events today until next weekGoogle CalendarService
- 5Get events for tomorrowGoogle CalendarService
- 6Get events for todayGoogle CalendarService
- 7Filter checks due next weekFilterLogic
- 8Filter checks due day beforeFilterLogic
- 9Filter checks due todayFilterLogic
- 10If item length is zeroIfLogic
- 11Aggregate check data for tomorrowAggregateLogic
- 12Aggregate checks data for todayAggregateLogic
- 13AggregateAggregateLogic
- 14Send reminder day before for checks dueTelegramService
- 15Send reminder on due date for checksTelegramService
- 16Send reminder week before for checks dueTelegramService
How it's built
- Starts on
- A clock
- Steps
- 16, with 1 branch
- Size
- Medium: a working afternoon
- Connects to
- Google Calendar, Telegram
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Google Calendar and Telegram accounts. You connect your own accounts after importing it; none are included.
What starts it?
It starts on a clock.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 16 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 16 steps before you point it at anything that matters.