Cron Job Every 20 minutes

Schedule a task to run every 20 minutes, 72 times each day. Use the cron string */20 * * * *, see the next 5 execution times, and copy Python, Node.js, Bash and n8n snippets.

Quick Answers

What does the "Every 20 minutes" cron expression mean?
This cron expression is "*/20 * * * *", which in plain English means: Schedule a task to run every 20 minutes, 72 times each day..
When will this cron expression run next?
With the expression "*/20 * * * *", the next execution times are Fri, Aug 14, 2026, 01:00:00 PM UTC, Fri, Aug 14, 2026, 01:20:00 PM UTC, Fri, Aug 14, 2026, 01:40:00 PM 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.
Explore the full Cron Cheat Sheet with all 50 schedules
Cron Expression
Copy this exact string into crontab, cron triggers, or schedulers.
*/20 * * * *

Human readable

Schedule a task to run every 20 minutes, 72 times each day.

Next 5 execution times

  1. 1Fri, Aug 14, 2026, 01:00:00 PM UTC
  2. 2Fri, Aug 14, 2026, 01:20:00 PM UTC
  3. 3Fri, Aug 14, 2026, 01:40:00 PM UTC
  4. 4Fri, Aug 14, 2026, 02:00:00 PM UTC
  5. 5Fri, Aug 14, 2026, 02:20:00 PM UTC
Python
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-20-minutes.py", comment="scheduled by crongen")
job.setall("*/20 * * * *")
cron.write()

print(f"Installed: */20 * * * * -> /usr/bin/python3 /var/www/job_every-20-minutes.py")

About the "every 20 minutes" cron schedule

The "every 20 minutes" cron schedule uses the expression "*/20 * * * *". This schedule fires 72 times per day, around the clock.

In plain English the cron string "*/20 * * * *" means: Every 20 minutes.

This cadence is a common choice for periodic sync jobs that refresh cached data or pull external feeds and generating interim snapshots and dashboards without overloading the server. 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.

Frequently asked questions