• Schedules
  • Uptime
  • Heartbeats
  • Status pages

A scheduler. A monitor. A status page. Are you getting it?

It's one tool. For you & your AI agent.

Run any URL on a schedule, know the moment your site or a job stops, and keep your customers posted on a status page. Set it up in the dashboard, or ask your agent.

Example
  • POST your-site.com/api/daily-report

    Every weekday at 9:30 · UTC200 OK
  • your-site.com182 ms · 99.98% uptime
  • Status pagecrontap.page/your-site
    your-site.com

    All systems operational

    WebsiteOperational
Start free

Free for 2 schedules or monitors. No card.

2.1k+ teams run their jobs on CrontapSee how it all fits together

One tool, no juggling

Stop juggling five tools for one job.

Schedules, uptime checks, heartbeats, your AI agent and a status page in one dashboard. One login, one bill, one place to look when something breaks.

Call any URL on a clock you can read.

Explore schedules
Schedules · Plain English or cronExample
POSTyour-store.com/api/sync-orders

every weekday at 9:30

30 9 * * 1-5 · Europe/London · next Tue 09:30

One Crontap account replaces
  • a cron service
  • an uptime checker
  • a heartbeat monitor
  • a status page tool
One login, one bill.

Schedules

Give it a URL and a time. Crontap makes the call.

A schedule is one HTTP request on a clock. Write when it runs in plain English, like “every weekday at 9:30”, or in cron, and pick the timezone it runs in. Test it before the first run. After that, server errors and timeouts retry with backoff, and every run lands in its history.

Example · Your schedules
ScheduleEarlierNext
  • health-check

    GET api.your-app.com/health

    every minute · UTC

    200 · 84ms

  • sync-orders

    POST your-store.com/api/sync-orders

    every 10 minutes · Europe/Berlin

    200 · 1.2s · 1 retry

  • summarize-tickets

    POST your-app.com/api/summarize

    every 30 minutes · UTC

    200 · 3.4s

  • weekly-digest

    GET your-blog.com/wp-cron.php

    every monday at 5am · Europe/London

    200 · 640ms

What every schedule comes with

  • When

    every weekday at 9:30

    Understood as 30 9 * * 1-5

    Next run Mon 09:30

    Plain English or cron

    Type “every weekday at 9:30” or 30 9 * * 1-5. Crontap shows the cron it understood and when it runs next, before you save.

  • One account, three clocks

    • uk-report05:00 Europe/London
    • us-digest09:00 America/New_York
    • jp-sync08:30 Asia/Tokyo

    A timezone per schedule

    Send the UK report at 5am London time and the US digest at 9am New York time, from the same account.

  • Before the first run

    Test run 200 OK412ms

    Response

    { "synced": 42 }

    Test before the first run

    Send the request once from the form and see the status code, the duration and the response before it goes live.

  • One run, three attempts

    1. #1503retry in ~1m
    2. #2timeoutretry in ~2m
    3. #3200recovered

    Retries with backoff

    Server errors, network errors and timeouts retry up to three times by default, about 1, 2 and 4 minutes apart. Pro can tune the curve.

  • Run history · last 14

    12 ok1 retried1 failed

    Every run on record

    Status, duration and error for each run, retries included. Free keeps the last 100 runs per schedule, Pro keeps 1,000.

  • Failed· after 3 retries

    502 Bad Gateway (12,003ms)

    upstream timed out

    Sent to email, Slack #ops

    Told when it fails

    When the retries are used up, Crontap sends the status code and the error by email on every plan, or to Slack, Discord or Telegram on Pro.

DIY vs Crontap

All the work, none of the steps.

Every team that runs jobs on a timer ends up building the same plumbing. Here is that list, and what replaces each line on Crontap.

If you build it yourself

  • A worker dyno or container that stays up just to keep time
  • IAM bindings or a service account for every target
  • A scheduler add-on per platform: Heroku Scheduler, Cloud Scheduler
  • Retry logic with exponential backoff
  • Alerting wired up to Slack or PagerDuty
  • A log pipeline to find out what ran last night
  • A deploy every time the cadence changes

With Crontap

  1. 1Paste the URL
  2. 2Say when
  3. 3Done
  • Nothing to host. Crontap keeps the clock.
  • Auth headers on the request, set once per schedule
  • One list for every app, host and timezone
  • Retries with backoff, on for new schedules
  • Email on every plan, Slack, Discord or Telegram on Pro
  • Status, duration and error for every run
  • Change the time in the dashboard. No deploy.

Uptime, heartbeats, alerts

Hear about it before your customers do.

Uptime monitors call your site on a timer and mark it down after two failed checks in a row. Heartbeats catch the job that never ran: it pings a secret URL when it finishes, and silence past the grace window is an alert. Email works on every plan; Slack, Discord and Telegram on Pro. A recovery message follows when it's fixed.

What broke

Uptime monitor · down

your-site.com is down

503 on 2 checks in a row

Where it goes

How it looks in Slack

Crontap · #ops

your-site.com is down. 503 on 2 checks in a row.

Integrations

Run your Zapier, Make and n8n flows on a clock.

Crontap can start a Zap, a Make scenario, an IFTTT applet or an n8n workflow by calling its webhook on a schedule. After a run, it can post the result to any URL you add.

Crontap MCP

Set up schedules and monitors by asking your agent.

Connect once over MCP. Your agent can create schedules, uptime monitors and heartbeats, and read what ran. Same account, same limits.

Status pages

Status pages people actually want to look at.

Put your monitors and heartbeats on a public page in about a minute, from a calm grid to a split-flap departures board. Free on every plan, with every template.

Use cases

Start from a job you already run.

Browse all use cases

Order syncs, Monday digests, cache warm-ups and wp-cron on quiet WordPress sites. Each guide shows the URL to call, the schedule to use and how to hear when it fails.

Works with your platform

  • WordPress
  • Shopify
  • HubSpot
  • OpenAI
  • Cloud Run
  • Vercel
  • Railway
  • Heroku
  • Ghost
  • Google Apps Script
  • Render
  • Netlify
  • Firebase
  • Fly.io
  • AWS Lambda
  • Zapier
  • Make
  • n8n
  • Slack
  • Discord
  • Telegram
  • Airtable

Same tool, one bill

Everything you'd juggle, under one login.

FAQ

Crontap questions, answered.

Is there a free tier?
Yes. Starter includes 2 combined schedules, uptime monitors, and heartbeats. It allows 1 uptime monitor at a 1-day cadence and 1 heartbeat at an hourly cadence, plus email notifications and 100 log entries per schedule. Pro starts at $2.99/mo with 3 to 20 combined items at 1-minute cadence. Ultra offers 25 to 1,000 combined items, API access, and priority support.
What's the shortest interval Crontap supports?
Every 1 minute on paid plans. That beats Vercel Cron on Hobby (once a day) and matches Google Cloud Scheduler (1 minute) without the per-target IAM dance Cloud Scheduler requires. GitHub Actions cron sits at a 5 minute minimum and can drift 15 minutes during peak per their own docs.
Do I need to know how to write cron expressions?
No. Crontap ships with templates for the most common patterns (hourly, daily, weekdays, monthly, etc.) and a plain-English scheduler (Describe it) so you never have to write `0 */4 * * *` unless you want to. If you do want to, we have a free cron expression debugger at tool.crontap.com/cron-debugger.
Can I get notified when a scheduled call fails?
Yes. Crontap retries server errors, timeouts, and connection failures with exponential backoff, then alerts you if the retries are used up. Email alerts are on every plan; Slack, Discord and Telegram channels are on Pro. Generic machine webhooks remain under Integrations. See alert channels and setup guides.
Do you support heartbeat / dead man's switch monitoring?
Yes. Create a heartbeat, ping its unique URL from your cron job or worker, and Crontap alerts you when expected pings arrive late or fail. Learn about heartbeat monitoring.
Can I publish a public status page?
Yes. Pick the uptime monitors and heartbeats your customers should see and publish them at crontap.page/<slug>, free on every plan with every template, incidents, maintenance, a status badge, RSS and status.json. Pro, from $2.99/mo, adds your logo, removes the Crontap branding and connects a custom subdomain. See status pages.

Ready when you are

All of it. One sign-up.

Start with one job or one site. Status pages are free on every plan, and Pro starts at $2.99 a month when you need every minute or Slack alerts.

Free for 2 schedules or monitors. No card.

GET

/wp-cron.php?doing_wp_cron=1

Running
Your next schedule

Schedule

"every 5 minutes"

Next

in 23s

2.1k+ teams · Millions of schedules running right now