Tools & Automation

Cron and Schedules

Run any prompt on any schedule.

Tell MoClaw what to do, when to do it, and where to send the result. Cron runs your prompts in the cloud at the time and frequency you set, then pings you with the output through any chat surface. Works for daily briefs, watcher loops, weekly digests, monthly reports, and one-shot reminders.

How it works

3 steps to wire up Cron and Schedules, no engineering required.

  1. 1

    Phrase the schedule in plain English

    Say 'every weekday at 8am' or 'every 30 minutes' or 'next Tuesday at 3pm'. MoClaw parses it into a real cron expression in your timezone.

  2. 2

    Tell MoClaw what to run

    Describe the workflow: read a feed, check a price, summarize a channel, watch a page. Anything you can ask in chat can be scheduled.

  3. 3

    Pick the destination

    Send the output as a Telegram DM, Slack message, Lark group post, email, or just back to your MoClaw web inbox.

Try saying

Real prompts you can paste into Cron and Schedules.

  • Every weekday at 8am, send me a Telegram brief with overnight Slack messages, calendar for the day, and inbox priorities.
  • Check the AWS status page every 5 minutes and notify me when any us-east-1 service goes red.
  • On the first of every month, generate a sales report from Stripe and email it to finance@.
  • In 2 hours, remind me to take the laundry out.

Step by step demo

What actually happens when you send the prompt.

Prompt 01 4 steps

“Every weekday at 8am, send me a Telegram brief with overnight Slack and calendar.”

What MoClaw does

  1. 1 Parses 'every weekday at 8am' into the cron expression 0 8 * * 1-5 in your timezone.
  2. 2 Schedules a recurring job and writes it to your Schedules dashboard.
  3. 3 At each fire, pulls overnight unread Slack threads and today's calendar events.
  4. 4 Composes a single Telegram DM under 200 words and sends it.
Result

Each weekday morning a Telegram DM lands at 8am: 'Tuesday brief. Overnight: 3 Slack threads need a reply. Calendar: 4 meetings starting 10am. Top priority: sign the design partner contract before the 11am call.'

Prompt 02 4 steps

“Check the AWS status page every 5 minutes and ping me when any us-east-1 service goes red.”

What MoClaw does

  1. 1 Schedules a recurring 5-minute job.
  2. 2 Loads the AWS status page in a sandboxed browser at each fire.
  3. 3 Parses the us-east-1 service health column and compares to the last run.
  4. 4 If any service flipped to red, sends a Slack message and pauses the watcher for 30 minutes to avoid spam.
Result

47 minutes later you get a Slack message: 'us-east-1 EC2 is red. Status page link. Watcher paused for 30 minutes; next check at 14:32. Reply resume to clear the pause.'

FAQ

Quick answers about pricing, privacy, and limits.

How granular can the schedule be?
Down to every 1 minute on paid plans, every 5 minutes on free. Cron expressions, plain English, and one-shot 'in N hours' all work.
Do scheduled jobs use my credits?
Yes. Each fire runs a real chat session, so it draws from your monthly credits or your BYOK key. You can set a per-job budget cap.
Can I see and edit my schedules?
Yes. Open Settings then Schedules to see every active job, pause it, edit the schedule, or read the run history.
What happens if a scheduled job fails?
MoClaw retries with exponential backoff (1 minute, 5 minutes, 30 minutes). If it still fails, you get a notification with the error and a one-click rerun.
Can I trigger a scheduled job from outside MoClaw?
Yes, via a webhook URL per schedule. Useful for chaining MoClaw to GitHub Actions, Zapier, or your own scripts.

Try MoClaw free.

1,000 credits a month, or bring your own key for unlimited usage.

Cancel anytime