Use case
Fire Make webhooks on any cadence without Make's schedule limits.
Make's internal schedule trigger counts as an operation per run, and minute cadence is plan-gated. Crontap is the external clock that fires the scenario's Webhook URL at zero ops cost for the trigger itself.
Free plan · no credit card required
The problem
Why this is painful without the right tool
- Make's internal schedule trigger consumes one operation per run, before the scenario itself does any work.
- Minute cadence is plan-gated; sub-15-minute schedules require a paid plan tier that only makes sense for high-volume use.
- Webhook-first scenarios prefer an external clock anyway; the Make Webhook trigger is free of ops cost when it fires.
- Multi-scenario teams have no central schedule view; the cron lives inside each scenario.
The fix
How Crontap solves it
Build the scenario in Make starting with a Webhook trigger. Copy the Webhook URL. Paste into Crontap and pick a cron. The scenario fires every time Crontap calls; the operations the scenario consumes are unchanged, but the schedule itself is now external and free.
*/10 * * * *The setup is two clicks. In Make, edit the scenario and pick a Webhook trigger; copy the Webhook URL. In Crontap, create a schedule, paste the URL, set the cron expression and the timezone. Save. The scenario runs on Crontap's clock from then on.
For multi-scenario teams, one Crontap schedule per scenario keeps the dashboard parseable. Failures alert to email / webhook (Slack / Discord / Telegram); the failure payload includes the run's status code, duration, and response body, so a Make scenario that returned a 5xx (paused scenario, webhook quota exhausted) shows up in the alert.
Cross-link: see the existing walkthrough at Integrate Crontap with Make webhooks for the click-by-click setup.
FAQ
Common questions
- Does this break Make's billing?
- No. The scenario still runs the same operations once it starts; the only thing that changes is who fires the trigger (Crontap, not Make Schedule). The internal Schedule trigger's ops cost goes away; the scenario's own ops cost is unchanged.
- What's the shortest interval Crontap supports?
- Every 1 minute on paid plans. Free tier available for slower cadences. Minute cadence on Make Schedule is plan-gated; minute cadence on Crontap is available on Pro across the board.
- Can Crontap send a payload?
- Yes. Paste a JSON body into the schedule's payload field. Crontap sends it on every run. The Webhook trigger in Make receives the payload and you can route it through subsequent modules.
Ready to fix it?
Point Crontap at any URL. Pick any cron. Done.
WordPress, Shopify, Railway, Cloud Run, Vercel, HubSpot, Ghost, your own box. If it answers HTTP, Crontap can drive it on a clock you can read, in the timezone that actually matters, and page you when something breaks.
Free forever tier ・ No credit card required
/wp-cron.php?doing_wp_cron=1
Schedule
"every 5 minutes"
Next
in 23s