A practical field guide from Automation Ace.
The short answer
Classic Zaps are built step by step in Zapier's visual editor. Next Gen Zaps are built by describing what you want to an AI agent, which writes, tests, and deploys the workflow as code that Zapier hosts. Next Gen Zaps add capabilities classic Zaps lack, such as unlimited list processing, nested loops, branches that rejoin, resilient error handling, and pause-and-resume. They are also newer, in early access, and ask you to trust and review AI-generated code.
For the capabilities in detail, see 7 things Next Gen Zaps can do that classic Zaps can't. For the build process, see how to build and deploy Next Gen Zaps.
Classic Zaps vs Next Gen Zaps at a glance
| Classic Zaps | Next Gen Zaps | |
|---|---|---|
| How you build | Visual Zap editor: pick a trigger, add steps, map fields | Describe it in plain language to an AI agent (in an MCP client like Claude, ChatGPT, Cursor, or the Zapier editor's built-in agent); the agent writes the workflow |
| What the Zap is | A configured sequence of steps | A TypeScript workflow hosted by Zapier, with a read-only visual diagram |
| Loops | Looping by Zapier with a 500-item cap; no nested loops | Process entire lists without the 500-item cap; nested loops supported |
| Branching | Paths, which do not rejoin | Branches that split and rejoin |
| Error handling | A failed step usually stops the run unless you configure error handling | Errors can be handled so one failure does not stop the whole run |
| Waiting | Delay steps and Human in the Loop | Pause mid-run for a human reply or scheduled follow-up, then resume |
| Drafts and versions | One draft at a time; version history | Multiple drafts at once; each publish saves a version you can branch from |
| Monitoring | Zap history, alerts, and manual fixes | Optional Agentic Management: an agent reviews runs, diagnoses failures, and prepares fixes |
| Availability | All plans | Early access by request on paid plans (Professional, Team, Enterprise) |
| Task usage | Action steps use tasks | Zapier says building, testing, and running do not use tasks during early access |
Details reflect Zapier's help documentation during early access and may change.
Classic Zaps: strengths
- Visual and approachable. Anyone can open the editor, see each step, and change a field mapping.
- Mature and predictable. Years of patterns, templates, and troubleshooting know-how.
- Available on every plan, with built-in tools like Filter, Paths, Formatter, and Code.
- Easy handoff to non-technical owners.
Limitations: the 500-item loop cap, no nested loops, Paths that cannot rejoin, and complex logic that often spills into Code steps or chains of linked Zaps. See multi-step Zap design.
Next Gen Zaps: strengths
- Natural-language building through an AI agent, including from MCP clients you already use. See what MCP is.
- More expressive logic: nested loops, rejoining branches, and full-list processing in one workflow.
- Resilience: per-item error handling and pause-and-resume for human replies or follow-ups.
- Software-style lifecycle: multiple drafts, published versions, and tests with sample input. See version control for automations.
- Agentic Management to watch runs and propose fixes, with you deciding how much it may do alone.
Next Gen Zaps: limitations and trade-offs
- Early access: availability is by request, features are still changing, and some classic conveniences may not have equivalents yet.
- Code under the hood: the workflow is TypeScript (Zapier documents a 200,000-character limit). The visual diagram is read-only, so reviewing or debugging deeply may require reading code.
- AI-generated logic needs review. Agents can misread requirements; test thoroughly and keep a person accountable. See human approval for AI workflows.
- Ownership and handoff: document what each workflow does so it is not a black box when the builder moves on. See what happens when the builder leaves.
- Pricing after early access has not been finalized in the documentation we reviewed; do not assume task-free running is permanent.
Which should you use?
- Simple trigger-and-action automations maintained by non-technical owners: classic Zaps.
- Large lists, nested data, or complex branching that strain classic Zaps: Next Gen Zaps.
- Long-running processes that wait on people or follow-ups: Next Gen Zaps, or classic Zaps with Human in the Loop.
- Teams already working with AI coding agents: Next Gen Zaps fit your workflow.
- Critical production systems: keep proven classic Zaps running and pilot Next Gen Zaps in parallel before migrating.
Request early access to Next Gen Zaps and start with one workflow that hits a classic Zap limit, such as a loop over more than 500 items.
Frequently asked questions
What are Next Gen Zaps?
Next Gen Zaps are a newer way to build Zapier automations: you describe what you want to an AI agent, and it writes, tests, and deploys the workflow as TypeScript code that Zapier hosts.
What is the difference between classic Zaps and Next Gen Zaps?
Classic Zaps are built step by step in the visual editor. Next Gen Zaps are built through an AI agent and support capabilities like unlimited list processing, nested loops, rejoining branches, resilient error handling, pause-and-resume, and multiple drafts.
Are Next Gen Zaps available to everyone?
Not yet. Zapier describes Next Gen Zaps as early access by request, available on paid plans (Professional, Team, and Enterprise).
Do Next Gen Zaps use tasks?
Zapier states that during early access, building, testing, and running Next Gen Zaps does not use tasks. Pricing after early access may differ.
Should I migrate my classic Zaps to Next Gen Zaps?
Not all at once. Keep proven classic Zaps running, pilot Next Gen Zaps on workflows that hit classic limits, and migrate once you have tested and documented them.
Disclaimer: Zapier features, plan availability, and settings can change. Confirm current details in Zapier's help documentation and Zapier's Next Gen Zaps help documentation. Next Gen Zaps are in early access, so features and availability are changing quickly before relying on a specific setting. This article may include links to apps, products, or services; some links may be affiliate links, which means Automation Ace may earn a commission at no extra cost to you.