Browse use cases by topic.

Every automation platform charges per task, including the ones that just exist to be a clock. The spokes here move the clock to Crontap and keep your task budget for actual work.

Most serverless platforms ship a built-in scheduler with one big constraint: UTC-only, fixed minimum interval, or coupled to deploys. The spokes here cover the work teams actually do.

Heroku Scheduler is fixed at 10 minutes. Railway has no native scheduler. Render and Fly.io mostly require always-on workers. The spokes here are the external HTTP cron pattern for each.

HubSpot workflows fire on contact events. Notion automations are limited. Airtable's automations cap at 15 minutes on lower plans. The spokes here drive each from the outside.

Most messaging APIs ship send endpoints but no scheduler. The spokes here are the recurring patterns: standup prompts, digest posts, class reminders, on-call rotations.

Bolt, Lovable, v0, Tempo, base44, create.xyz and Replit ship the app, not the scheduler. The spokes here add a real clock without making your AI builder generate a cron daemon.

Stripe and Lemon Squeezy ship rich webhook eventing, no scheduler. The spokes here are the recurring billing work: reconciliations, retries, payroll, dunning runs.

Health-check work splits two ways: actively pinging services on a clock, and proving that a flow you run elsewhere still runs. The spokes here cover both.

wp-cron only fires when a visitor lands on the site. The spokes below cover the patterns teams use Crontap for on WordPress and WooCommerce stacks.

Shopify Flow fires on events. WooCommerce depends on wp-cron. The spokes below cover the polling, syncing and reconciliation work that needs a real clock behind it.

Bubble's recurring workflows charge units per run. Webflow has no native scheduler at all. The spokes here drive both from the outside on any cadence.

AI agents that run once aren't the interesting case. Brand monitors, daily summarisers, sentiment pipelines and recurring research are. The spokes here cover the cron behind them.

Most spokes here are technically webhook patterns. This page is the explicit one: any URL, any cadence, any payload, on a real cron.