Cron Job Every 6 hours
Schedule a task every six hours, four times per day. Use the cron string 0 */6 * * *, see the next 5 execution times, and copy Python, Node.js, Bash and n8n snippets.
Quick Answers
- What does the "Every 6 hours" cron expression mean?
- This cron expression is "0 */6 * * *", which in plain English means: Schedule a task every six hours, four times per day..
- When will this cron expression run next?
- With the expression "0 */6 * * *", the next execution times are Fri, Aug 14, 2026, 06:00:00 PM UTC, Sat, Aug 15, 2026, 12:00:00 AM UTC, Sat, Aug 15, 2026, 06: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 */6 * * *Human readable
Schedule a task every six hours, four times per day.
Next 5 execution times
- 1Fri, Aug 14, 2026, 06:00:00 PM UTC
- 2Sat, Aug 15, 2026, 12:00:00 AM UTC
- 3Sat, Aug 15, 2026, 06:00:00 AM UTC
- 4Sat, Aug 15, 2026, 12:00:00 PM UTC
- 5Sat, Aug 15, 2026, 06:00:00 PM 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-6-hours.py", comment="scheduled by crongen")
job.setall("0 */6 * * *")
cron.write()
print(f"Installed: 0 */6 * * * -> /usr/bin/python3 /var/www/job_every-6-hours.py")Related schedules
About the "every 6 hours" cron schedule
The "every 6 hours" cron schedule uses the expression "0 */6 * * *". This schedule fires 4 times per day.
In plain English the cron string "0 */6 * * *" means: On the hour, every 6 hours.
This cadence is a common choice for long-running build or maintenance pipelines that tolerate multi-hour gaps and aggregating logs or telemetry into batched reports. 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.