A practical field guide from Automation Ace.
Short answer: Next Gen Zaps are Zapier workflows that you describe in plain language to an AI agent, which writes the workflow as TypeScript code, tests it, and publishes it for Zapier to host and run. They handle things classic Zaps struggle with (full-list processing, nested loops, branches that rejoin, per-item error handling, and pause-and-resume), and they can be watched by an agent that diagnoses failures. At the time of writing they were in early access by request on paid plans.
Short answer
- Built by: an AI agent, from your description.
- Built as: TypeScript that Zapier hosts, with a read-only diagram.
- Better at: big lists, nested data, complex branching, resilience, long-running steps.
- Managed by: you, optionally with Agentic Management.
- Status: early access on paid plans; details may change.
What Next Gen Zaps are
Classic Zaps are configured step by step in a visual editor. Next Gen Zaps flip that: you explain the outcome, the agent writes software, and Zapier runs it on the same app connections you already use. It is still Zapier, but the unit of automation is now code written by an agent rather than a list of configured steps. For a full side-by-side, see classic Zaps vs Next Gen Zaps.
Anatomy of a Next Gen Zap
| Part | What it is |
|---|---|
| The builder | An AI agent: the Zapier editor's built-in agent, or an MCP client such as Claude, ChatGPT, Cursor, Claude Code, or Codex connected to Zapier |
| The workflow | TypeScript code that Zapier hosts and runs, shown as a read-only visual diagram |
| Connections | Your Zapier app connections, chosen with the agent |
| Drafts and versions | Several drafts at once; each publish saves a version you can branch from |
| Tests | Draft runs with sample input before publishing |
| Agentic Management | An agent that reviews runs, diagnoses failures, and prepares fixes, with the autonomy you allow |
Why it matters
| Classic Zap limit | Next Gen Zaps approach |
|---|---|
| Looping capped at 500 items, no nested loops | Process full lists; nest loops |
| Paths cannot rejoin | Branch and rejoin |
| A failed step usually stops the run | Handle errors per item and keep going |
| Long processes split across Zaps | Pause for a reply or follow-up, then resume |
| One draft at a time | Multiple drafts and published versions |
| Built click by click | Described in plain language, built by an agent |
Each of these is covered in 7 things Next Gen Zaps can do that classic Zaps can't, and the logic patterns in Next Gen Zaps for complex workflows.
How you build one
- Get access (early access by request on paid plans at the time of writing; on Team plans an owner or admin requests it).
- Connect an agent: the built-in editor agent or an MCP client; see connecting Zapier MCP to AI clients.
- Describe the workflow: trigger, apps, steps and rules, and failure behavior.
- Review the plan, pick connections, and let the agent draft.
- Test with sample input, including edge cases.
- Publish a version and watch early runs.
Step-by-step: how to build and deploy Next Gen Zaps.
Early-access limits to know
- Early access applies to your whole account, including all workspaces, according to Zapier's documentation at the time.
- Zapier advised against running your most sensitive workflows through Next Gen Zaps during early access.
- Sub-Zaps were not supported, and one Next Gen Zap could not call another.
- Some Enterprise features, such as the audit log, were not yet supported.
- The workflow code has a documented size limit (200,000 characters).
- Building, testing, and running did not use tasks during early access; Zapier described standard task-based pricing afterward. Check current pricing.
Who should try them now
- Teams whose classic Zaps hit loop caps, need nested data, or have duplicated Path endings.
- Builders comfortable reviewing AI-generated logic, or with someone who can read TypeScript.
- Anyone wanting a pilot before broader adoption; see how to migrate existing automations.
What it says about the future of automation
Automation is moving from configuring steps to describing outcomes. Builders spend less time clicking and more time specifying, reviewing, testing, and governing; see how Next Gen Zaps change the role of the Zapier builder. Agents and Next Gen Zaps also fit together rather than compete; see Next Gen Zaps vs AI agents. Zapier's AI workspace points the same way; see beyond Zaps with Sidekick.
Frequently asked questions
What are Next Gen Zaps?
Next Gen Zaps are Zapier workflows built by describing them in plain language to an AI agent, which writes the workflow as TypeScript code, tests it with sample input, and publishes versions that Zapier hosts and runs on your existing app connections.
What can Next Gen Zaps do that classic Zaps cannot?
They can process entire lists beyond the 500-item loop cap, run nested loops, branch and rejoin, handle errors per item so one failure does not stop the run, pause for a reply or follow-up and resume, and keep multiple drafts and versions.
How do I build a Next Gen Zap?
With early access, connect an AI agent (the Zapier editor’s agent or an MCP client), describe the trigger, apps, steps, rules, and failure behavior, review the plan and connections, test the draft with sample input, then publish a version.
Are Next Gen Zaps available on all Zapier plans?
At the time of writing they were in early access by request on paid plans such as Professional, Team, and Enterprise. Check Zapier for current availability.
Do Next Gen Zaps use tasks?
During early access, Zapier said building, testing, and running Next Gen Zaps did not use tasks, and described standard task-based pricing afterward. Check Zapier’s current pricing before relying on it.
Disclaimer: Next Gen Zaps were in early access at the time of writing, by request on paid plans; capabilities, limits, and pricing after early access may change, so confirm current details in Zapier's help center. 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.