GitHub Actions Cron Schedule Generator

Build complete .github/workflows/*.yml files with on.schedule cron definitions and manual triggers.

AWS EventBridge Rule (CloudFormation & Terraform)

Configure schedule and executable to generate copy-paste deployment code.

Cron Expression

Command / Handler Target

# Terraform AWS EventBridge Rule
resource "aws_cloudwatch_event_rule" "scheduled_task" {
  name                = "scheduled-task"
  description         = "Scheduled cron trigger for scheduled-task"
  schedule_expression = "cron(0 9 * * 1-5 *)"
}

# Target trigger
resource "aws_cloudwatch_event_target" "lambda_target" {
  rule      = aws_cloudwatch_event_rule.scheduled_task.name
  target_id = "TriggerLambda"
  arn       = "arn:aws:lambda:us-east-1:123456789012:function:my-function"
}

Dialect:

5 fields (UTC only)

Cron Expression (GitHub Actions (schedule))

Plain EnglishWeekly

“Every Monday at 12:00 AM”

Runs every monday at 12:00 am. Evaluated according to GITHUB cron specifications.

Evaluation Timezone

Popular Presets:

Frequently Asked Questions

Everything you need to know about Cron expressions, syntax rules, and platform nuances.

In what timezone are GitHub Actions scheduled workflows run?

GitHub Actions workflows are strictly evaluated in UTC (Coordinated Universal Time). You cannot configure regional timezones directly inside the cron field in workflow YAML.

Why did my scheduled GitHub Actions workflow run late?

At peak times (notably the top of the hour :00), high traffic across GitHub Actions runners can delay execution by a few minutes. Scheduling at off-peak minutes (e.g. 17 or 42) helps avoid runner queuing.