Put work on a schedule
Take a result you already got once, and have it arrive without you asking again.
Schedule outcomes you have seen at least once. Scheduling something you have never run produces a weekly disappointment instead of a weekly report.
Create it
1. Open the employee → Routines → add one (*on a clock*)
2. Write the instruction in plain language — the same words that worked in chat
3. Pick the cadence from the menu — every hour, every day at a time, weekdays, every week, every month — or write a cron expression under *Advanced*
4. Choose where the result lands, and whether the employee continues its last conversation or starts fresh
You can also just ask in chat — "do this every Friday at 5pm" — and the routine appears under Routines.
Give the recurring version a quality bar
A one-off gets your judgement live; a scheduled one does not. Say what "good" looks like inside the instruction — the length, the sections, what to leave out, what to flag rather than decide.
Run it once before trusting it
Every job can be run on demand, paused, and inspected — each run keeps its output and its log.
Start from the library instead
The Library ships ready-made jobs per role. Pick one, choose the employee, and it installs with a sensible schedule you can then edit.
Endpoints, payloads and the full job model are in Jobs. For work that starts on an event rather than a clock, see Set up a trigger.