A correction matters here: Schedule by Zapier does not count toward task usage. Zapier triggers never use tasks. Successful action steps do. A minute-level Zap with two successful actions can still use 86,400 tasks in a 30-day month, but all of those tasks come from the actions, not from the clock.
If you replace Schedule with a Catch Hook and point Crontap at it, your Zapier task usage does not fall merely because the trigger changed. The reason to move the clock is control: five-field cron, a per-schedule IANA timezone, configurable HTTP retries, uptime and heartbeat monitoring, or an AI Integration that transforms the HTTP response before forwarding it.
How Zapier Schedule billing works
Zapier's pricing model is straightforward: a task is a successful action step. Triggers, including Schedule by Zapier and Catch Hook, do not consume tasks. Filters and Paths also do not count. An errored or halted action does not count, while a successful action does.
The Zapier pricing page lists current task allowances and cadence features. Check it directly because plan names, allowances, and intervals change. The stable accounting rule is documented separately:
- Schedule trigger: zero tasks.
- Catch Hook trigger: zero tasks.
- Successful action: one task unless Zapier documents the built-in app as task-free.
- Pro+ Autoreplay: automatically retries errored steps up to five times, with increasing delays, and sends the error notification after the final attempt fails.
The practical math therefore comes from the workflow body. A Zap with one successful action uses one task per triggered run. A Zap with three successful actions uses three. Swapping Schedule for Catch Hook leaves that count unchanged.
The corrected math: actions, not schedule fires
A minute-level Zap fires 43,200 times in a 30-day month. That number is still useful, but multiply it by successful actions:
- No action runs after a filter: zero tasks.
- One successful action: 43,200 tasks.
- Two successful actions: 86,400 tasks.
- Three successful actions: 129,600 tasks.
Those totals are identical whether Schedule by Zapier or a Catch Hook starts the Zap. External cron does not reclaim trigger tasks because there were no trigger tasks to reclaim.
The external-cron pattern
The pattern is one of the cleaner refactors in Zapier-land. You do not migrate the Zap. You do not replace the actions. You only swap the trigger.
Crontap (cron) → HTTPS POST → Zapier Catch Hook → rest of the ZapCrontap fires the Catch Hook, which costs zero Zapier tasks. Schedule by Zapier also costs zero tasks. The Zap runs as before, with the same filters, paths, and actions. Only the clock and its operational controls changed.
Step 1: Swap the Zapier Schedule for a Catch Hook
Open the Zap. Edit the trigger. Replace the existing Schedule by Zapier trigger with a Catch Hook from Webhooks by Zapier.
- In the Zap editor, click the trigger step.
- Search for and select Webhooks by Zapier.
- Pick Catch Hook as the event.
- Press Continue. No trigger configuration is needed for a basic Catch Hook.
- Zapier shows you a webhook URL. Copy it. Keep this tab open.
The downstream steps (the filters, the actions, the formatter steps) all stay exactly as they are. Each one still consumes one task per fire when it runs, which is the part you actually want to pay for.
Step 2: Fire the Catch Hook from Crontap
Head to Crontap and create a new schedule.
- URL. Paste the Catch Hook URL you copied from Zapier.
- Method.
POST. - Headers. Optional. Add
Authorization: Bearer <your token>if you want to filter on the Zap side, or leave headers empty if the Catch Hook is your only auth boundary. - Cadence. Type plain English ("every 5 minutes") or paste a cron expression. Crontap previews the next 5 fires inline so you can sanity-check before saving.
- Timezone. Pick the IANA zone that matches the schedule's intent. Per-Zap timezones are a Crontap feature; the Schedule trigger uses your account-wide timezone setting.
- Failure alerts. Choose connected email, Slack, Discord, or Telegram channels in Notifications, or add a machine webhook under Integrations. The alert fires if the final attempt fails, with status, duration, size, error summary, and attempt history in the payload.
Press Perform test to fire a real request before you trust the cadence. If the Catch Hook returns 200, you are done. If you see 4xx, the Catch Hook URL is wrong. If you see 5xx, Zapier itself is having a bad day and the alerting just proved itself.
Step 3: Keep the rest of the Zap
This is the part that makes the migration cheap. The downstream steps do not change.
Filters still filter. Paths still path. Formatters still format. Actions still send to Slack, write to Sheets, post to HubSpot, whatever you set up. Each successful downstream action consumes a task as before. The trigger used no tasks before and uses no tasks after.
If you want to validate the Catch Hook is the right URL, you can also test by hitting the Catch Hook URL with curl from your laptop. The Zap should fire and you should see it in the Zap history exactly like a Schedule-triggered run.
Fix this in 60 seconds with Crontap. Free forever tier. No credit card. Schedule your first job →
Worked example: a 5-minute Zap with two actions
A five-minute Zap runs 8,640 times in a 30-day month. If every run successfully performs a search action and posts to Slack, that is 17,280 Zapier tasks. Schedule by Zapier contributes zero additional tasks. A Crontap-fired Catch Hook also contributes zero.
The Crontap plan is therefore an added operational tool, not a task-saving arbitrage. It can be worth from $2.99/mo when the team needs a per-schedule timezone, real cron syntax, retry rules for the webhook delivery, a test-run response, or monitoring that remains visible outside Zapier.
When Zapier Schedule is still the right call
External cron is a shape, not a religion. There are cases where the built-in Schedule by Zapier trigger is still the right answer.
- Daily and weekly Zaps. The built-in trigger is simpler and free in task accounting.
- Zaps covered by Autoreplay. Pro+ can retry temporary action errors up to five times without adding another scheduler.
- Zaps that need to run inside Zapier's exact account-wide timezone. If the Schedule trigger's account timezone is what you want and you do not need per-Zap zones, the built-in is simpler.
- One Zap, one schedule, no other targets. If Zapier is the only platform you fire scheduled work into, adding an external scheduler is one more service to operate. The wedge appears when you have multiple platforms (Zapier plus Make, plus n8n, plus Vercel, plus your own backend) and want a single dashboard for all of them.
For per-Zap timezones, real cron expressions, configurable HTTP retry outcomes, uptime, heartbeats, AI response transforms, or one view across multiple platforms, the external cron pattern can read cleaner.
For the head-to-head decision page with the at-a-glance table, see Crontap vs Zapier Schedule. For a step-by-step walkthrough of the Catch Hook setup with screenshots, see the existing Integrate cron with a Zapier webhook post; the same shape applies here.
Pricing math you can take to your boss
Count the successful Zapier actions per run, multiply by the number of runs, and ignore the trigger because it costs zero tasks. Then price Crontap separately for the scheduling and monitoring controls you need. If Zapier Schedule and Autoreplay already cover the workflow, adding Crontap will not save task spend.
FAQ
Will my Zap still work after the swap?
Yes. You replace the trigger with a Catch Hook (Webhooks by Zapier) and Crontap fires it on your chosen cadence. Everything downstream of the trigger keeps running exactly as before, with the same filters, paths, and actions you already configured.
Will Zapier still log my Zap runs?
Yes. Catch Hook fires show up in the Zap history exactly like Schedule-triggered runs did. The only thing that changes is what kicked them off.
Does the Catch Hook trigger consume a Zapier task?
No. Zapier documents that trigger steps do not count toward task usage. Successful downstream action steps consume tasks.
Will I save money on every Zap?
Not from the trigger swap. Task usage remains based on successful actions. Crontap may save engineering time or supply missing controls, but it does not remove downstream Zapier task charges.
Can Crontap fire multiple Catch Hooks?
Yes. Each Zap is its own Catch Hook URL, each schedule is its own row in Crontap. One Crontap account can fire as many Zaps as you have, plus your Vercel cron routes, your Cloud Run jobs, and anything else with an HTTPS endpoint.
What about Make and n8n?
Same pattern works for both. Replace the platform's built-in scheduler with a webhook trigger and point Crontap at the webhook URL. See the related Make and n8n posts for platform-specific notes.
What is Crontap's minimum cadence?
Every 1 minute on Pro. The same as Zapier Team and Company plans, except the Crontap clock costs zero per fire.
References
- Zapier pricing
- Schedule by Zapier docs
- How Zapier measures task usage
- Zapier Replay and Autoreplay
- Webhooks by Zapier docs
Related on Crontap
- Crontap vs Zapier Schedule, side by side. The head-to-head decision page with the at-a-glance table.
- Cron jobs for Zapier webhooks use case. The use-case-first guide for Zapier teams wiring up an external clock.
- Integrate cron with a Zapier webhook. The full step-by-step walkthrough with screenshots.