With Next Gen Zaps, you can use any MCP client that supports Model Context Protocol (MCP), such as a web-based chatbot or a coding agent, to build and deploy automations by describing them in plain language instead of using the visual Zap editor. Your MCP client chooses the right app connections, wires up the steps, and deploys the workflow to Zapier for you.
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.
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
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.
Build and deploy your workflow
- In your MCP client, describe the Zap workflow 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.
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 for an event and resume later. |
| Long follow-up that can stop | "Email trial users on day 3, 7, and 14. Stop if they upgrade." | Durable waits 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.
Pricing during early access
Next Gen Zaps are free during early access on Professional, Team, and Enterprise plans. Building, testing, and running Next Gen Zaps does not use tasks, and Zapier does not bill you for them.
When billing begins
When billing begins, Next Gen Zaps will use the same task-based pricing as classic Zaps:
- Each app action costs 1 task, the same as in a classic Zap.
- AI by Zapier steps follow your plan's tiered task pricing.
- Each fetch call costs 1 task. A fetch call is a request that custom code in your workflow makes to an outside app or API.
- Only successful actions and successful fetch calls count toward your task usage. Failed actions do not use tasks.
- Logic inside your workflow, such as filters, formatting, loops, and branching, does not use tasks.
- Composing, editing, testing, and publishing a Next Gen Zap does not use tasks.
After billing begins, the tasks your Next Gen Zaps use count toward your monthly task usage and are billed according to your plan.
Advance notice
Zapier will share full pricing details and a start date by email and in-product messages before billing begins. Nothing you build or run during early access will generate a bill.
Limitations
- Next Gen Zap's TypeScript code has a 200,000-character limit.
-
You can only import Zaps that you own.
- If you want to import someone else's Zap, duplicate it or change ownership of it to yourself first.
Enterprise customers
Early access is enabled for your entire account, including all workspaces. You cannot limit it to specific workspaces or 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)
- Workspaces
- 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 via Relay
- Static IP
- SOC 2 audit scope
- Self-serve data deletion and retention controls
- Priority support and Technical Account Manager
- Task limits and billing (Next Gen Zaps are not billed during early access)
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.