Scheduled jobs

api/cron.js is a special file (not an HTTP route). Default-export a map of job name → handler. Handlers receive (env, ctx):

// api/cron.js
export default {
  async daily_digest(env, ctx) {
    const { results } = await env.DB
      .prepare("SELECT email FROM subscribers WHERE digest = 1")
      .all();
    for (const row of results) {
      await env.EMAIL.send({
        to: row.email,
        subject: "Your daily digest",
        html: "<p>Here's what's new…</p>",
      });
    }
  },

  async cleanup_temp(env, ctx) {
    // …
  },
};

An array of { name, handler } objects works too — use whichever reads better.

• set_cron_job — create or update a schedule, pointing at a job name from api/cron.js.
• list_cron_jobs — see an app's scheduled jobs.
• run_cron_job — trigger a job immediately (handy for testing).
• delete_cron_job — stop a schedule. (The handler stays in api/cron.js until you remove it.)

In practice you just ask your assistant: “run daily_digest every morning at 7am” — it writes the handler and calls set_cron_job.

The number of jobs per app, and whether you can schedule more often than once a day, depend on your plan — see Limits & quotas.