Get started with Next Gen Zap workflows

With Next Gen Zap workflows, you can use any AI 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 AI 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 AI client to build and deploy your first Next Gen Zap.

Available on plans:

Free

Professional

Team

Enterprise

Early Access

Next Gen Zap workflows is in early access. Contact Zapier support and select Early Access Products > Next Gen Zap Workflows to request it. This feature has limited availability and is in active development.

Before you begin

  • You need an AI client that supports Model Context Protocol (MCP), such as a web-based chatbot or a coding agent.
  • You need a connected account for each app you want to use in your workflow.
  • Familiarity with Zapier MCP is helpful but not required.

Install Zapier MCP

  1. Follow the Zapier MCP quickstart to create an MCP server and connect it to your AI client.
  2. In your AI client, tell it to use the zapier:build-workflows skill.
    • This skill installs the tools your workspace needs and confirms your Zapier account has early access to Next Gen Zap workflows.

Build and deploy your workflow

  1. In your AI client, describe the Zap workflow you want to create in plain language.
  2. Review your AI client's suggestions. It will walk you through choosing the right app connections, creating and testing the workflow, and deploying it to Zapier.
  3. Once your workflow is deployed, go to the Zapier Workflow Manager to review its history and any activity, or ask your AI 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 Zap workflows 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 Zendesk refunds to #finance, wait for approval, then refund in Stripe." 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 Zap workflows. 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.

Next steps

You installed Zapier MCP, connected your apps, and used an AI client to build and deploy your first Next Gen Zap. Now:

Was this article helpful?
0 out of 0 found this helpful