Estimate Whether a Workflow Fits Zapier's Free Plan
Estimate task usage for the full account and check each workflow's plan requirements. A quiet month can fit the task limit while a single workflow still needs a paid feature.
Worked example
Two one-action workflows in one account
Workshop signup → create one CRM contact Typical month = 52 signups × 1 task = 52 Busy month = 84 signups × 1 task = 84 Return request → create one help desk ticket Typical month = 31 requests × 1 task = 31 Busy month = 39 requests × 1 task = 39 Combined typical month = 83 tasks Combined busy month = 123 tasks At 100 available tasks, the busy month is 23 tasks over. Check each app's eligibility separately.
Steps
- List each Classic Zap you want to keep. Record the triggering event, the actions it performs and how many events you expect in a typical and busy month.
- For the simple third-party actions in this worksheet, multiply the number of events by the number of successful actions per event. The trigger uses no tasks. Look up any special step rates in Zapier's task usage guide.
- Sum the workflows that share your account and compare to the current allowance in Billing and usage. Also account for any Zapier MCP usage that draws on the same allowance.
- Check the plan requirements separately. Zapier's Free plan supports one trigger and one action per Zap. Review connected apps and features before assuming a workflow created in a paid trial will keep running.
What to check
- Use your actual billing cycle and any other assets already consuming the allowance. Record the cycle close date alongside the estimate.
- Estimate retries when a replay repeats actions that already succeeded. Run history can help you compare forecast volume with actual usage.
- When a workflow sends a message and creates a record on every event, count both actions and verify that the plan permits the second action.