“Remind me on Friday”, and on Friday it does

A reminder tool is two different things: taking the request, and saying it back on time. They usually become two scenarios, and then you go looking for why reminders get set and never arrive. Here it is one scenario with a branch at the front.

What is inside

1. A message or an alarm — the entry. Both arrive here.
2. Who woke us — a branch on data.trigger: a person wrote, or the schedule fired.
3. The upper branch parses the request into text and a date, stores the row and confirms. The document is assembled in the write node’s Document field; done: false stays a boolean instead of turning into a string.
4. The lower branch pulls the unfinished ones and sends them to Telegram.

Keeping this as two scenarios means keeping two places that hold the same thing: the collection name, the row shape, the date field. One branch is cheaper.

What to set up for yourself

• Today’s date. The parsing prompt carries {{ nodes.entry.data.triggered_at }}, the run time from the platform. The model does not know what day it is, and without that substitution “on Friday” becomes a date out of its head.
• Filtering by date. The lower branch currently takes everything unfinished. Once there are many reminders, add a condition on the due field.
• Marking things done. The done field is written and nobody updates it yet: for a reminder to arrive once, the records need updating after the send.
• The thin edge to the query. The edge into “What is due today” is an execution edge: an ordinary data edge would be taken as a filter. And you iterate output.docs.

What to connect

A collection under Tables, a Telegram bot and the Schedule target on the Publish tab. Fire it once a day in the morning: an hourly schedule is pulled back to half-hourly on the free plan anyway, and reminders become a stream.