BackendBench
Coffee

Home โ€บ GitHub Actions โ€บ Every Monday at 9:00 AM

GitHub Actions cron

GitHub Actions cron expression: every Monday at 9:00 AM

To run a GitHub Actions job every Monday at 9:00 AM, use:

0 9 * * 1

At 09:00 UTC, on Mon.

Your week at a glance
fewer more runs

Upcoming runs

#LocalUTCFrom now

Copy-ready code

Why use this schedule

A weekly start-of-week job that fires every Monday morning. Teams use it to open the week with a fresh report, a reset counter, or a reminder that lands before the first meeting.

First runs, as an example

Starting from 1 January 2027, evaluated in UTC:

#Date and time (UTC)
1Mon, 04 Jan 2027, 09:00:00
2Mon, 11 Jan 2027, 09:00:00
3Mon, 18 Jan 2027, 09:00:00
4Mon, 25 Jan 2027, 09:00:00
5Mon, 01 Feb 2027, 09:00:00
6Mon, 08 Feb 2027, 09:00:00

Every Monday at 9:00 AM in every dialect

SystemExpression
GitHub Actions (this page)0 9 * * 1
Quartz0 0 9 ? * 2
Spring0 0 9 * * 1
Crontab0 9 * * 1
Kubernetes0 9 * * 1
AWS EventBridge0 9 ? * 2 *
JenkinsH 9 * * 1
node-cron0 9 * * 1
Apache Airflow0 9 * * 1
Azure Functions0 0 9 * * 1
Google Cloud Scheduler0 9 * * 1

Need to translate a different expression? Use the cron converter.

Ready-to-use GitHub Actions config

Drop this into your project. The expression is the one above.

Workflow trigger
on:
  schedule:
    - cron: "0 9 * * 1"

The GitHub Actions fields, in order: minute (0-59), hour (0-23), day-of-month (1-31), month (1-12), day-of-week (0-6, 0 = Sunday).

Things to watch out for in GitHub Actions

The common mistake with this schedule

In Quartz and EventBridge, 1 means Sunday, so 0 9 ? * 1 fires on Sunday. Monday is 2, or write MON.

Frequently asked questions

How do I run a GitHub Actions job every Monday at 9:00 AM?

Use 0 9 * * 1. At 09:00 UTC, on Mon.

What is the every Monday at 9:00 AM cron expression in other systems?

Quartz: 0 0 9 ? * 2; Spring: 0 0 9 * * 1; Crontab: 0 9 * * 1. The table on this page lists every dialect.

Which time zone does GitHub Actions use for this schedule?

GitHub Actions schedules are always UTC. Convert your local time to UTC before writing the expression.

Similar GitHub Actions schedules

More tools you might need