Cron Job Every Tuesday at 9 AM
Run a cron job every Tuesday at 9:00 AM. Use the cron string 0 9 * * 2, see the next 5 execution times, and copy Python, Node.js, Bash and n8n snippets.
Quick Answers
- What does the "Every Tuesday at 9 AM" cron expression mean?
- This cron expression is "0 9 * * 2", which in plain English means: Run a cron job every Tuesday at 9:00 AM..
- When will this cron expression run next?
- With the expression "0 9 * * 2", the next execution times are Tue, Aug 18, 2026, 09:00:00 AM UTC, Tue, Aug 25, 2026, 09:00:00 AM UTC, Tue, Sep 01, 2026, 09:00:00 AM UTC.
- How do I use this cron expression?
- Copy the exact string into crontab, cron triggers, or any scheduler such as GitHub Actions, n8n or Docker. Pre-built code snippets for Python, Node.js, Bash, Docker, GitHub Actions and n8n are included on this page.
0 9 * * 2Human readable
Run a cron job every Tuesday at 9:00 AM.
Next 5 execution times
- 1Tue, Aug 18, 2026, 09:00:00 AM UTC
- 2Tue, Aug 25, 2026, 09:00:00 AM UTC
- 3Tue, Sep 01, 2026, 09:00:00 AM UTC
- 4Tue, Sep 08, 2026, 09:00:00 AM UTC
- 5Tue, Sep 15, 2026, 09:00:00 AM UTC
from crontab import CronTab
from datetime import datetime
# Install: pip install python-crontab
cron = CronTab(user=True)
job = cron.new(command="/usr/bin/python3 /var/www/job_every-tuesday-at-9am.py", comment="scheduled by crongen")
job.setall("0 9 * * 2")
cron.write()
print(f"Installed: 0 9 * * 2 -> /usr/bin/python3 /var/www/job_every-tuesday-at-9am.py")Related schedules
About the "every Tuesday at 9 AM" cron schedule
The "every Tuesday at 9 AM" cron schedule uses the expression "0 9 * * 2". This schedule fires once per week.
In plain English the cron string "0 9 * * 2" means: At 09:00 AM, only on Tuesday.
This cadence is a common choice for weekly routines like report generation or team digests on a set weekday and periodic archive or snapshot tasks that repeat every week. The schedule is deliberately kept simple: copy the string into any cron-aware scheduler (crontab, Vercel Cron, GitHub Actions, n8n, Docker or Kubernetes CronJob) and the run will repeat automatically — steady, with no manual triggering.