Cron in plain English

Build-along · ~12 min at your own keyboard

Scheduled triggers are the 'while you sleep' half of automation: every weekday at 6am, every Friday at 4, first of the month. Modern platforms take the schedule in plain English. Rule stands: schedule the deterministic scripts, not the unattended LLM. This is the engine behind lead-follow-up automation that never forgets a day-3 check-in.

Your starter: Sunday week-view on a schedule

Workflow steps

Make it yours: Set the day and hour you actually plan, list your courses, and keep the stop rule: a file that trips the name scan never opens, and no retry is automatic.

SCHEDULE: [weekday] at [hour], for courses [list]

1. Build each week view listed from the unit folder and the calendar. Skip any course with no change since last week and say so.
2. Stop on any file whose structure changed since last week, and on any file where a student's name, an ID or a grade beside a name appears. No student goes in by name past this step.
3. For the files that pass, write the week view to the course tab with the break days marked.
4. One-line summary per course: built, stopped, flagged, with counts.

Never retry a stopped file. Never open a source outside the list. The stopped file is a question for a person, and anything it asks about a child is [YOUR CALL: ...]. The decision stays yours.

The coach checks that what you paste back is your own work. The starter pasted back unchanged won't pass.

Do this

0/4

Share what happened

Paste the schedule, evidence of two untouched automatic runs, and their outputs (trimmed).