Use case
Fire Webhooks by IFTTT applets on any cadence.
IFTTT's Date & Time service trigger caps your scheduling at hourly, daily, weekly, or monthly. Crontap is the external clock that fires Webhooks by IFTTT applets on any cadence, in any IANA timezone, with retries on 5xx and central failure alerts.
Free plan · no credit card required
The problem
Why this is painful without the right tool
- IFTTT's Date & Time trigger only supports hourly, daily, weekly, and monthly cadences; sub-hourly is not available.
- Multi-applet scheduling has no central view; the cadence lives inside each applet rather than in one dashboard.
- Pro plan tiers gate higher applet counts and faster polling, but still cap the Date & Time service at the same coarse cadences.
- Webhooks-by-IFTTT applets prefer an external clock anyway; the trigger is a plain HTTPS POST that any scheduler can fire.
The fix
How Crontap solves it
Build the applet in IFTTT starting with a Webhooks (Maker) trigger. Copy the trigger URL (the maker.ifttt.com/trigger/{event}/with/key/{key} form). Paste into Crontap and pick a cron expression plus a timezone. The applet fires on Crontap's clock from then on.
*/15 * * * *The setup is two clicks. In IFTTT, edit the applet and pick a Webhooks (Maker) trigger; copy the URL with your event name and personal key. In Crontap, create a schedule, paste the URL, set the cron expression and the IANA timezone. Save. The applet runs on Crontap's clock from then on.
For multi-applet teams, one Crontap schedule per applet 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 an applet that returned a 4xx (rate-limit, missing event, key revoked) shows up in the alert.
Cross-link: see the existing walkthrough at Integrate Crontap with IFTTT (Twitter applet) for the click-by-click setup.
FAQ
Common questions
- Does this break IFTTT's billing?
- No. The applet still runs the same way once it starts; the only thing that changes is who fires the trigger (Crontap, not the IFTTT Date & Time service). Your IFTTT plan tier still gates applet count and overall polling cadence; the trigger itself is just an HTTPS POST that costs nothing extra to fire.
- What's the shortest interval Crontap supports?
- Every 1 minute on paid plans. Free tier available for slower cadences. IFTTT's Date & Time service does not offer minute cadence on any tier; Crontap fills that gap with the Webhooks (Maker) trigger.
- Can Crontap send a payload to IFTTT?
- Yes. Webhooks by IFTTT accept up to three values (value1, value2, value3) plus a JSON body. Paste them into the schedule's payload field. Crontap sends the body on every run; the applet receives it and you can route it through subsequent ingredients.
Related guides
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