What an AI cron job actually is
A classic cron job is a line on a server that runs a script at a set time. It is reliable, but it only does exactly what the script says, and someone has to write and maintain that script. An AI cron job keeps the reliability of the timetable and replaces the brittle script with an agent that can read a web page, compare it with last week, decide what matters and write a short summary for a person.
In Crons, each AI cron job (we simply call it a cron) has three parts. A schedule with a cron expression and a timezone. A list of steps, such as a web fetch, an AI reasoning step, a memory write and a Slack message. And a run log that records every step, input, output, retry and timing, so you can see exactly what happened on Tuesday at 8 AM.
You do not need to write the cron expression yourself. Type "Every Monday at 8 AM check our 20 competitors and send pricing changes to Slack" and Crons turns that sentence into a schedule and a step plan you can review before saving. Read more about how that parsing works on the natural language schedules page.
Classic cron versus an AI cron job
Both approaches run on time. The difference is what happens inside each run and who has to keep it working when a source changes.
| Aspect | Server cron job | AI cron job in Crons |
|---|---|---|
| How you define it | Cron line plus a script | One plain English sentence |
| Reading messy sources | Breaks when a page layout changes | AI step reads the page like a person would |
| Remembering last run | You build your own storage | Built in memory with diffs and "only new" |
| Failures | Silent unless you add monitoring | 3 retries with backoff, then an email or Slack alert |
| Sensitive actions | Runs without asking | Approval gate before emails, CRM writes, public posts |
| Audit trail | Whatever the script logs | Full run log of every step and output |
If you already monitor server jobs and want to know where Crons fits next to that, the cron monitoring comparison explains the difference between watching jobs and running AI jobs.
What each run does step by step
- 1The schedule fires at the time and timezone you set, or you press Run now.
- 2Fetch steps collect inputs: web pages, an API response, a Google Sheet, a HubSpot list or a headless browser session.
- 3A memory read loads what the cron saw last time, so the next step can compare old and new.
- 4An AI reasoning step filters, classifies, summarizes or drafts text based on your instructions.
- 5Conditions decide whether anything is worth sending. No change means no noise.
- 6An approval gate pauses the run if the next action emails customers, writes to a CRM or posts publicly.
- 7Delivery steps send results to Slack, Gmail, Notion, Google Sheets, HubSpot or a webhook, and the memory write stores the new state.
Every one of those steps appears in the run log with its timing. When a step fails, Crons retries it up to three times with backoff before marking the run as failed and alerting you.
Good first AI cron jobs for business teams
The best candidates are tasks someone already does on a calendar reminder. If a researcher spends two hours every Monday checking competitor pricing pages, that is roughly a hundred hours a year that a cron can take over, with the researcher only reading the summary.
- Competitor pricing watch every Monday, with changes only, sent to a Slack channel.
- Lead list refresh every weekday morning, new companies matching your criteria added to a Google Sheet.
- Customer health digest every Friday, accounts with falling usage summarized for the success team.
- Invoice reconciliation on the first of each month, mismatches flagged for finance to approve.
- SEO audit of key pages every week, broken titles and missing descriptions reported in Notion.
Each of these exists as a ready template. Browse them on the templates page and adjust the sentence instead of starting from a blank cron.
How often AI cron jobs can run on each plan
Frequency and volume depend on the plan. Usage counts per billing period, so deleting a cron never returns runs you already used. Crons alerts you at 80 percent of a limit and stops before going over it.
| Plan | Active crons | Runs per month | Minimum frequency |
|---|---|---|---|
| Starter | 10 | 300 | Every 1 hour |
| Pro | 50 | 1,500 | Every 15 minutes |
| Teams | Unlimited, fair use | 6,000 | Every 5 minutes |
A weekly cron uses about four or five runs a month, a daily one about thirty. Full plan details are on the pricing page.
Safety rules built into every run
A job that runs while nobody is watching needs guardrails. Crons never executes payments. Steps that email customers, write to a CRM or post in public channels can wait for a human approval, and you see the exact draft before you approve it. Dry run mode lets you test a cron end to end without sending anything. Credentials for API steps are stored encrypted and never shown in the run log.
Frequently asked questions
Do I need to know cron syntax to create an AI cron job?
No. You describe the schedule in plain English, for example "every weekday at 7 AM Berlin time", and Crons writes the cron expression and timezone for you. You can still edit the expression directly if you prefer.
What happens when a step fails during a run?
The step is retried up to three times with increasing waits between attempts. If it still fails, the run is marked as failed, the run log shows the error, and you get an alert by email or Slack.
Can an AI cron job send emails to customers on its own?
Only if you allow it. Customer emails, CRM writes and public posts can sit behind an approval gate, so the run pauses until someone on your team approves the exact message.
Does a cron remember what it found last time?
Yes. Memory read and write steps store the previous result, so the cron can report only new items or only changes instead of repeating the same list every run.
Can I run a cron outside its schedule?
Yes. Every cron has a Run now button, and on Pro and Teams you can also trigger it from an inbound webhook or the REST API.
Is there a free plan for AI cron jobs?
No. You can try the demo on the homepage without an account to see the parsed schedule, steps and a sample result. Saving needs an account and running needs a paid plan starting with Starter.