March 14, 2026

Setting Up AI Cron Jobs: The Complete Guide for 2026

Why Cron Jobs Change Everything

Here's what most people don't get about AI agents: they're reactive by default.

You ask. It answers. You close the chat. That's it. Next morning, it has no idea what you discussed yesterday.

But what if your AI could work while you sleep?

What if it could:

Check your inbox every 15 minutes and reply to urgent emails
Monitor your product sales and alert you to anomalies
Find new leads and send outreach automatically
Generate daily reports and summaries before you wake up

That's what cron jobs enable. And in this guide, I'll show you exactly how to set them up.

What Are AI Cron Jobs?

Cron jobs are scheduled tasks that run automatically at set intervals. Traditional cron runs scripts. AI cron jobs run agents that can:

Make decisions based on context
Use tools (search, email, databases)
Learn from previous runs
Produce nuanced outputs (not just "hello world")

With OpenClaw, you configure cron jobs in your workspace. The agent reads its instructions, executes the task, logs results, and waits for the next run.

Step-by-Step: Setting Up Your First AI Cron Job

Prerequisites

OpenClaw installed and running
At least one channel configured (Telegram, Discord, etc.)
API keys for any tools you need (email, search, etc.)

Step 1: Create a Cron Configuration File

In your workspace, create crons/:

mkdir -p crons

Step 2: Define Your First Cron Job

Create crons/daily-briefing.json5:

{
  name: "daily-briefing",
  schedule: "0 8 * * *",  // 8 AM daily
  enabled: true,
  description: "Generate morning briefing with tasks, calendar, weather",
  instruction: `You are a briefing agent. Create a morning summary for the user.
  
  1. Read MEMORY.md to understand ongoing projects
  2. Check today's date and generate appropriate greeting
  3. Include: weather, top 3 tasks, any deadlines, motivation quote
  4. Format as markdown with emojis
  5. Send via the default channel`,
  
  model: "bailian/glm-5",
  timeout: 60000
}
            

Step 3: Enable Cron Execution

In your config.json5, add:

{
  crons: {
    enabled: true,
    path: "./crons",
    defaultInterval: 900000  // 15 minutes minimum
  }
}
            

Step 4: Test It

openclaw cron run daily-briefing

You should receive your first briefing. Adjust the instructions until it's perfect, then let it run autonomously.

Real-World Examples

Example 1: Lead Generation Agent

Runs every 15 minutes. Finds new potential customers, validates them, and sends personalized outreach.

{
  name: "lead-outreach",
  schedule: "*/15 * * * *",
  enabled: true,
  description: "Find and contact new leads",
  instruction: `You are a sales outreach agent for ReceiptSaver.
  
  1. Search Kijiji for new contractors in Canadian cities
  2. Filter for: construction, plumbing, electrical, HVAC
  3. Score each lead based on: business name quality, description completeness, location
  4. Select top 3 leads not yet contacted
  5. Write personalized email mentioning their specific services
  6. Send via Brevo API
  7. Log to leads-outbound.md with timestamp`,
  
  model: "qwen-coder-next",
  timeout: 120000
}
            

Result: 31 personalized emails sent while you sleep.

Example 2: Content Idea Generator

Runs every 6 hours. Monitors trends and generates content ideas.

{
  name: "content-ideas",
  schedule: "0 */6 * * *",
  enabled: true,
  description: "Generate social media content ideas",
  instruction: `You are a content strategist.
  
  1. Check current trends on Twitter, TikTok, YouTube
  2. Read recent MEMORY.md for project updates
  3. Generate 5 content ideas relevant to: AI automation, CS student life, building in public
  4. For each idea: title, hook, 3 key points, call to action
  5. Save to content-ideas.md`,
  
  model: "bailian/glm-5",
  timeout: 90000
}
            

Example 3: Monitor Product Sales

Runs every hour. Alerts you to new purchases or anomalies.

{
  name: "sales-monitor",
  schedule: "0 * * * *",
  enabled: true,
  description: "Check for new Stripe payments",
  instruction: `You are a sales monitor.
  
  1. Query Stripe API for payments in the last hour
  2. If new payment: congratulate the user, log details
  3. If refund: alert immediately with reason
  4. If unusual pattern (5+ failed payments): warn
  5. Send summary to default channel`,
  
  model: "bailian/glm-5",
  timeout: 30000
}
            

Best Practices

1. Start Small

Don't automate everything at once. Start with one cron job. Get it working perfectly. Then add more.

2. Set Appropriate Intervals

15 minutes — Fast-moving data (leads, social mentions)
1 hour — Monitoring (sales, analytics)
Daily — Summaries, reports, planning

Don't run complex agents too frequently. You'll burn through API credits.

3. Always Log Results

Every cron should write to a log file. You'll need this for:

Debugging when things break
Understanding patterns over time
Proving ROI to yourself

4. Build in Safety Checks

{
  name: "safe-outreach",
  schedule: "*/30 * * * *",
  maxEmailsPerDay: 50,
  cooldownAfterError: 3600000,
  instruction: `...`
}
            

5. Monitor and Adjust

Check your cron logs daily at first. Tweak instructions based on outputs. The agent learns from better prompts.

Common Pitfalls

Setting It and Forgetting It

You need to review outputs initially. The agent won't be perfect right away.

Over-Automation

Don't automate things that need human judgment. Use AI for repetition, not nuance.

Ignoring Rate Limits

APIs have limits. Brevo: 300 emails/day on free tier. Stripe: 1000 requests/sec. Check before you scale.

No Error Handling

What happens when the API fails? Your cron should have a fallback: log the error, alert you, retry later.

Tools You Need

Brevo	Email sending	300 emails/day
Open-Meteo	Weather data	Unlimited
Brave Search	Web search	2000 queries/month
Stripe	Payment monitoring	Free
Supabase	Database	500MB

Want the Full Guide?

I packed everything into my OpenClaw Ultimate Setup Guide. 8 chapters, copy-paste configs, 15+ cron templates.

Get the Guide

Final Thoughts

Cron jobs are where AI agents go from "cool chatbot" to "actual employee."

You define the task once. It runs while you sleep. It handles the repetition. You focus on the creative, strategic work that actually moves the needle.

Start with one cron job. Get it working. Then scale.

Your future self will thank you.