A reminder an hour before, and exactly one
The schedule fires often, the reminder arrives once: the scenario remembers what it has already said.
What the scenario looks like
- Execute + Data
- Data
- Execute
- LLM
A reminder an hour ahead is the most useful thing a calendar does, and the most irritating when it arrives three times. The check runs every half hour and a meeting stays inside the “next hour” window for two of them — so something has to remember what was already said.
What is inside
- Scheduled trigger — the entry.
- Meetings in the next hour queries the calendar.
- Who has already been told reads the collection of markers.
- What to remind about — the model, given both the meetings and the list of already-sent: the decision is made once, in one place.
- The branch, the Telegram send, and a marker written back into the same collection.
The collection here is not data but memory between runs: “we already mentioned this one”. Remove the last two nodes and a person gets each reminder twice, and fixing that afterwards takes longer than these two nodes did.
What to set up for yourself
- The “next hour” window is set by the query boundaries and the prompt.
- The reminder text. Currently the time and the title. The location is the obvious next thing to add.
- Cleaning up markers. The collection grows. It is worth clearing monthly — or adding a date to the marker and deleting old ones.
What to connect
A CalDAV calendar, a Telegram bot, a collection under Tables and the Schedule target. Fire it every half hour: the free plan will not go faster anyway, and for an hour’s notice that is enough.