Next Gen Zaps turn the work you describe to an AI tool into a workflow that keeps running on Zapier. You can build one from an MCP client, an AI tool that supports Model Context Protocol (MCP), such as Claude, ChatGPT, Gemini, or Cursor. You can also build one on Zapier with the AI assistant in the Workflow Manager. Your AI chooses the right app connections, wires up the steps, and deploys the workflow to Zapier for you.
Next Gen Zaps run alongside your Classic Zaps. Your Classic Zaps keep running unchanged, and you choose if and when to import one.
A Next Gen Zap also differs from a Code step in a Classic Zap. Whereas a Code step replaces a single step, a Next Gen Zap is a complete workflow that Zapier runs from start to finish.
By the end of this tutorial, you'll have used an MCP client to build and deploy your first Next Gen Zap.
Available on plans:
Free
Professional
Team
Enterprise
Early AccessNext Gen Zaps is in early access by request. Sign up at https://zapier.com/workflow/early-access. If you’re on a Team plan, the request must come from an account owner or admin. If you’re on an Enterprise plan, contact Support for access. This feature has limited availability and is in active development.
NoteIf your Enterprise account uses workspaces, you can turn on early access for individual workspaces, such as a sandbox. Your account must still be added to the early access list first. After that, the owner or a super admin of your account goes to the early access page while in each workspace they want to grant access to. To turn on early access for all workspaces at once, contact Zapier support.
Before you begin
- You need a connected account for each app you want to use in your workflow.
- Familiarity with Zapier MCP is helpful but not required.
Set up Zapier MCP
Next Gen Zaps works through Zapier MCP. On its own, Zapier MCP lets your MCP client run actions in your apps when you ask. Next Gen Zaps adds the ability to build and deploy a Zap that keeps running on its own afterward.
If you've never used Zapier MCP:
- Follow the Zapier MCP quickstart to create an MCP server and connect it to your MCP client.
-
Tell your MCP client to use the
zapier:build-workflowsskill.- This skill installs the tools your workspace needs and confirms your Zapier account has early access to Next Gen Zaps.
- When you’re done, refresh your MCP tools list.
If you already use Zapier MCP:
- Tell it to use the
zapier:build-workflowsskill. - You may need to refresh your MCP tools list.
Claude can take 3 to 12 hours to refresh its tools list on its own. If you use Claude Desktop, restart the app to refresh the list right away.
You can also build a Next Gen Zap on Zapier without an MCP client. In the Zapier left sidebar, click Automations, select Next Gen Zaps, then click + Create. You can create a new workflow and build it with the AI assistant, or import a Classic Zap that you can edit.
Importing creates a copy. Your original Classic Zap keeps running unless you turn it off, so leaving both on can cause duplicate runs. Read Import a Classic Zap into a Next Gen Zap for the steps, and Use the Workflow Manager to build and view your Next Gen Zaps for details.
Build and deploy your workflow
- In your MCP client, tell it to use the
zapier:build-workflowsskill, then describe the Zap you want to create in plain language. - Review your MCP client's suggestions. It will walk you through choosing the right app connections, creating and testing the workflow, and deploying it to Zapier.
- Once your workflow is deployed, go to the Zapier Workflow Manager to review its history and any activity, or ask your MCP client for a direct link to the workflow it created.
Your Next Gen Zap runs in Zapier, not inside your MCP client. This makes it different from an automation that runs inside an AI chat. A Next Gen Zap runs on its trigger or schedule without a chat window open, and you can also run it on demand at any time from your MCP client, the API, or the Workflow Manager. It keeps a full history of its runs, follows your Zapier account's permissions, and can use any app you connect to Zapier. It can also send custom API requests through your existing app connections, so you do not need to add separate credentials. It runs the same way no matter which MCP client you used to build it.
If a run fails, such as after a renamed field or an expired connection, an agent can diagnose the problem and prepare a fix. This is called Agentic Management, and it is on by default. After successful runs, the agent can also suggest improvements, such as turning an AI step that keeps making the same decision into a fixed step that runs faster and more predictably. You control what the agent can change without your approval. Read Agentic Management in Next Gen Zaps to learn more.
Use cases to try
Not sure where to start? Try one of the following ideas. Each one highlights something Next Gen Zaps can do that a Classic Zap cannot.
| What to try | Example prompt | What is new |
|---|---|---|
| Process a whole list | "Find every HubSpot contact untouched for 90+ days and add them to a re-engagement list." | No 500-item loop cap. For very large lists, process in batches instead of all at once so you do not trip the connected app's rate limits. Start with a few hundred records and scale up. |
| Reconcile two systems | "Check every row in my Sheet against my Stripe charges and flag mismatches." | Loop your full dataset and compare as you go. |
| Sync that survives failure | "On a closed Salesforce deal, create records in QuickBooks, Asana, and Slack. Skip any that fail and report back." | Catch an error and keep going. |
| Route, then merge | "Send enterprise leads to a rep, the rest to nurture, then save all to HubSpot and post to #leads." | Branches split and rejoin. |
| Loops inside loops | "For each Airtable client, total their open QuickBooks invoices into one digest." | Nested loops with a summary at the end. |
| Wait for a person | "Post new Zendesk escalations to #support-leads, wait for a manager's reply, then update the ticket priority." | Pause until an event arrives or a time limit passes, whichever comes first, then resume. |
| Long follow-up that can stop | "Email trial users on day 3, 7, and 14. Stop if they upgrade." | Durable waits of up to a year that you can cancel mid-run. |
Security considerations
Use judgment about which Zapier account, app connections, and data you make available while testing Next Gen Zaps. If an agent has access to private data, is exposed to untrusted instructions, and is allowed to send data elsewhere, it could take actions you did not intend, including sharing sensitive information.
Start with low-risk workflows and app connections. Avoid connecting accounts that contain highly sensitive data, such as legal documents, financial records, or private company files.
If you want a stricter safety boundary, use a separate Zapier account, less-sensitive app connections, or a dedicated test workspace.
When the Agentic Management agent applies a fix, it publishes the change as a new version of your workflow. You can review exactly what changed in the version history.
Pricing during early access
Starting December 1, 2026, Next Gen Zaps use tasks. Until then, they are free during early access on Professional, Team, and Enterprise plans. Learn how Next Gen Zaps and the Zapier SDK are billed to understand what counts as tasks, what does not, and how to check usage.
If your MCP client runs app actions through Zapier MCP while it builds, such as fetching sample data, each successful tool call uses tasks at the Zapier MCP rate. Your AI tool may also charge you for the tokens it uses.
Limitations
Next Gen Zaps have limits on code size, how long a run can wait, sharing, and how long Zapier keeps your data. Read Next Gen Zap limitations for the full list.
Enterprise customers
You cannot limit early access to specific users. To turn off early access, contact Zapier support.
Do not run your most sensitive workflows through Next Gen Zaps during early access.
Some Enterprise features are not supported in Next Gen Zaps during early access, and some are not yet confirmed to work the same way:
Governance and audit
- Audit log
- Log Streams
- Change History (per asset)
- Action restrictions
- Custom data retention
- Analytics (Admin Center)
- Approval requests (publish approval)
- API Scanner
Collaboration and permissions
- Sharing and per-asset permissions (viewer role only; editor role is unavailable)
- Folders and folder permissions
- Managed app connections
- Offboarding
Workflow and management
- Alerts page
- Sub-Zaps
- Global, Zap, and System variables
- Bring Your Own Model
- Templates
- Zap notes
- Premium app entitlements
- Autoreplay, flood protection, and polling customization
- Timezone and locale
- Manual editing parity
Compliance, infrastructure, and support
- Raw API access
- Static IP
- SOC 2 audit scope
- Self-serve data deletion and retention controls
- Priority support and Technical Account Manager
Learn more about these features on the Zapier pricing page.
Next steps
You installed Zapier MCP, connected your apps, and used an MCP client to build and deploy your first Next Gen Zap. Now:
- Share feedback or book time with a product manager to help shape Next Gen Zaps.
- Check your workflow's activity anytime in the Zapier Workflow Manager.
- Read What is Zapier MCP? to understand how your MCP client connects to your Zapier apps.
- Read Use the Workflow Manager to build and view your Next Gen Zaps to understand the Workflow Manager layout.
- Read Create Next Gen Zap drafts and versions to publish your changes and review earlier versions.
- Read Agentic Management in Next Gen Zaps to let an agent monitor a workflow and fix it when a run fails.