Crontap

Schedule recurring API calls with cron syntax.

Crontap calls your endpoints on a schedule you write in cron or plain English. Pick a frequency and a timezone, test the call once, and forget about it.

The Crontap homepage. The headline reads “Run schedules, not servers” next to a live list of example schedules and their next run times.
The front door at crontap.com

What it is

A scheduler that just makes the call

Crontap does one thing: it calls a URL on a schedule. Give it an endpoint and tell it when. No server to run, no cron daemon to babysit.

Write the schedule as a cron expression when you want precision, or in plain English when you do not. Every schedule has its own timezone, so a job set for 09:00 in Copenhagen stays at 09:00 when the clocks change.

Uptime monitoring and heartbeats live in the same account and use the same notification list. Between them they catch the call that failed, the URL that stopped answering, and the job that never ran.

Why it is built this way

The ideas behind it

  1. 01

    Write it either way

    Cron expressions when you want precision. Plain English when you would rather not count asterisks.

  2. 02

    Timezones that behave

    Each schedule keeps its own timezone. Daylight saving never shifts your jobs by an hour.

  3. 03

    Test before you save

    Send the request while you are still editing it and read the real response. Re-run any schedule by hand later.

  4. 04

    Know when it breaks

    Failed runs email your notification list instead of landing in a log you never open.

Flow

How it works

  1. 01

    Describe the request

    Method, URL, headers and body. If it is an HTTP call, Crontap can send it.

  2. 02

    Pick the schedule

    A cron expression or a plain sentence, plus the timezone it runs in.

  3. 03

    Test it once

    Run the call now and read the real response. Adjust before you save.

  4. 04

    Hear about failures

    Crontap keeps the run history and emails you when calls start failing.

Specifics

What you get

  • Cron expressions, or plain English like “every weekday at 09:00”
  • A timezone per schedule, so daylight saving does not move your jobs
  • Test the call before you save it. Re-run it any time after.
  • Custom method, headers and body for each scheduled request
  • Email alerts when a scheduled call starts failing
  • Calendar and list views of everything you have scheduled
  • Public REST API to manage schedules from code, on the Ultra plan

Screens

What it looks like

A closer look at Crontap.

The integrations section of the Crontap site. It lists Slack, Discord and Telegram for alerts, and Zapier, Make, IFTTT and n8n for automation.
Notifies and triggers the tools you already use
The Crontap pricing page with three plans side by side: Starter at $0, Pro at $4.99 a month and Ultra at $11.99 a month, each listing its combined item limit.
Utility pricing, not platform pricing

From crontap.com

“Run schedules, not servers.”

Schedule any HTTPS call on any cadence, from every minute to quarterly. Replaces WordPress wp-cron, beats Vercel Cron's hourly limit on Hobby, skips the Cloud Scheduler IAM dance. Pages you when something breaks.