Cron and scheduling are the difference between remembering to do a chore yourself and putting it on a calendar that actually fires. Time is the trigger.
Think about an office opening checklist. Every morning at 8:00, unlock the office. Every Friday at 4:00, send the weekly report. Every 15 minutes, check for an expected message. Nobody makes a fresh decision each time: the schedule says when to look, the checklist says what to do. Cron is an old Unix scheduling system, but people now use the word loosely for any scheduled task, nightly, weekly, or every five minutes.
How it shows up
Scheduled work usually isn’t AI. A script can pull a transcript, move a file, or check an inbox on a cron with no model involved. AI enters later, if you ask a model to understand, summarize, or decide something. In a WorkDesk-style system, a scheduled task might pull new calendar transcripts into intake every hour or refresh a dashboard each morning. That’s automation, but it’s different from an agent making judgment calls. Cron sits beside other triggers: a webhook fires because something happened, like a form submission; a scheduled job fires because time passed; a queue holds work until it’s ready to process; a hook fires around a tool event.
Why you care
The trigger changes the design. If you want a daily digest, schedule it. If you want an instant reaction to a Stripe payment, use a webhook. Cron is how software keeps a simple promise: do this thing at the right time, every time.