Blog · Automation platforms

Cron jobs for Zapier, Make, n8n and IFTTT

Every automation platform ships a built-in schedule trigger that almost works. These posts cover the gaps (hourly floors, task counts, missing timezones) and the webhook pattern that closes them.

About this topic

Automation platforms

12 itemsBlog

Zapier's Schedule trigger floors at hourly on the free plan, charges a task per fire, and doesn't expose real cron syntax. Make's scheduled scenarios run on a per-operation budget that compounds at high cadence. n8n's schedule node is fine self-hosted, less fine on n8n Cloud. IFTTT's time-driven applets don't expose minute-level cadence. Every one of them, though, ships a webhook trigger that fires the moment an HTTP request lands.

That webhook trigger is the wedge. Drop a Webhooks by Zapier trigger (or Custom Webhook on Make, Webhook node on n8n, Maker webhook on IFTTT) into the workflow, copy the URL, and point Crontap at it. The schedule trigger is no longer the bottleneck: Crontap fires on real cron syntax, in any IANA timezone, down to 1 minute on Pro, with custom headers and JSON payloads. The workflow runs exactly as designed, just on a clock you actually control. The posts below walk each platform's exact wiring, plus a cron syntax cheat sheet for every cadence you'll reach for.

Blog on Automation platforms

12 items

Related on Crontap

The same Automation platforms topic, from other angles.

FAQ

Common questions on Automation platforms

Zapier's built-in schedule already works. When does the external pattern pay off?
When you need cadences below the free plan's hourly floor, want real cron syntax instead of dropdowns, or care about per-Zap timezones. Pairing Webhooks by Zapier with Crontap also helps task-count budgets, since one Crontap fire equals one task, not a watcher tick plus the action.
Does Make's webhook trigger work the same way as Zapier's?
Yes. Make exposes a Custom Webhook trigger. Copy the URL into a Crontap schedule, configure the cadence and timezone, and the scenario runs on the schedule you set instead of Make's own scheduling layer.
Self-hosted n8n. Do I still need an external scheduler?
Probably not for the schedule node itself. The external pattern is useful when you want a single dashboard across n8n, Zapier, Make, IFTTT, and your own backend, or when you want failure alerts that don't depend on n8n being up.
IFTTT only fires hourly on free. Can the external pattern get me to minute-level?
Yes, by wiring an IFTTT Webhooks (Maker) trigger and pointing Crontap at it. The applet still runs the actions you've configured; the time trigger gets replaced by the webhook trigger and the cadence comes from Crontap.

More from Crontap

Topics across the site.

Every topic Crontap covers, in one row. Each one has its own page on the blog surface.

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

GET

/wp-cron.php?doing_wp_cron=1

Running
Your next schedule

Schedule

"every 5 minutes"

Next

in 23s