The Zapier Zap step limit is 100 steps, including every step inside paths. During a free trial only the first 30 steps run, and each action step can hold up to 1,000 fields. If you need more than 100 steps, Zapier says to split the work into multiple Zaps.
Why a branching Zap hits 100 sooner than you think
Picture a lead-routing Zap. One trigger, a filter, then paths for four regions, each with eight steps to format data, update a CRM, post to Slack and send an email. That's already over 35 steps, and every new path adds another batch. The limit counts every step inside every path, not just the ones a single run passes through.
Steps and tasks are counted separately, and this is where people get confused. A task is counted each time an action step runs successfully. Trigger, filter and certain built-in tool steps don't count as tasks. They do still sit in your Zap, though, so they count toward the 100 steps.
The limits in one table
| Item | Limit | Applies to |
|---|---|---|
| Steps per Zap (including paths) | 100 | All Zaps |
| Steps that run | First 30 | Free trial |
| Fields per action step | 1,000 | Every action step |
| Instant trigger requests | 20,000 per 5 minutes before 429 | Per user |
| Polling trigger requests | 200 per 10 minutes before runs are held | Free or trial plan, per Zap (as of Nov 2026) |
| Private app requests | 100 per 60 seconds | Free and Professional plans |
| Private app requests | 5,000 per 60 seconds | Team and Enterprise plans |
| Flood protection threshold | 100+ events at once | Polling triggers |
Every row comes from the Zapier Help Center's Zap limits article.
Counting steps before you build
It's worth sketching the Zap on paper first. Count the trigger, every filter and path step, then every action inside every path. If you're past 70 before you've added error handling, you'll want to plan the split now rather than rebuild later. It's much easier to design two Zaps than to cut one in half once it's live.
When the 100 steps run out
Zapier's answer is simple: separate the process into multiple Zaps. A common pattern is one Zap that catches and cleans the data, and a second that does the routing and actions. Splitting also makes each Zap easier to test and fix.
If you're on a free trial, watch the 30-step rule. Only the first 30 steps of a Zap run during the trial, so a long Zap may look broken when it's simply stopping where the trial stops.
The 1,000 field limit per action step counts standard and custom fields in your app. Most people never get near it, but a CRM with hundreds of custom fields can.
Other limits that hold runs
When you reach your task limit, Zap runs are held rather than lost, and you can replay them from Zap History. Zapier emails you as you approach and reach the limit, so keep an eye on those messages.
Instant-trigger Zaps get 429 errors if they go over 20,000 requests every 5 minutes per user. On a Free or trial plan, as of Nov 2026, Zaps with polling triggers are held if they exceed 200 requests every 10 minutes per Zap. Polling flood protection holds runs when 100 or more events trigger a Zap at once, and replayed runs then process at 1 per second.
One more practical rule: triggers and path conditions can't be moved, and steps can only be moved or pasted within limits, not between different Zapier accounts or browsers. Plan the structure before you build a big Zap, because rearranging it later is fiddly.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Other automation options
n8n documents configurable workflow timeouts for self-hosted setups, which gives you more control if you run it yourself. Slack's Workflow Builder lets anyone except Frontline Members build workflows from a template or from scratch, which suits simple automation inside Slack. My n8n and Zapier comparison looks at when each makes sense.
My advice for long Zaps
Design for two or three focused Zaps rather than one giant one. Count the steps inside every path as you plan, keep filters early so they stop runs before the heavy steps, and check Zap History when anything looks stuck. If the build is getting beyond you, hiring a Zapier, Make or n8n expert can save you days.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
How many steps can a Zap have?
Up to 100, including steps within paths.
What happens on a free trial?
Only the first 30 steps of a Zap run.
How many fields can a step have?
Each action step is limited to 1,000 fields.
What if I need more than 100 steps?
Split the process into multiple Zaps.
Do filters count as tasks?
No. Trigger, filter and certain built-in tool steps don't count as tasks, though they still count as steps.
