Zapier starts charging for Next Gen Zaps on 1 December

Since late September, Zapier customers on paid plans have been able to try Next Gen Zaps for free. These are a newer type of workflow that people can build by prompting an AI tool such as Claude or ChatGPT, or by using the visual editor or writing code. The free period has an end date. Zapier's workflows page says billing for Next Gen Zaps starts on 1 December 2026, and its task usage help article, updated on 5 November, sets out how those runs will be counted. Any NZ business that moved workflows across during early access has less than three weeks to work out what they'll cost.

What Zapier has confirmed

Zapier announced Next Gen Zaps on 23 September 2026. The headline features were loops, unlimited paths, code editing and a monitoring agent that watches runs and diagnoses failures. According to the Get started guide, last updated on 6 November, Next Gen Zaps are available on Professional, Team and Enterprise plans and are free until 1 December. Free plan users can't access them.

Pricing follows Zapier's existing task model. Each app action costs one task, the same rate as a Classic Zap, and from 1 December every completed Next Gen Zap run uses at least one task, according to Zapier's billing documentation. Filters, formatting, loops and branching don't use tasks on their own. The workflows page adds two charges that are easy to miss: an agent's external call to read app data costs one task per call, and so does each outside service call made by custom code. Zapier's own example is a loop over thousands of records, which will use far more tasks than a two-step workflow. The Get started guide also notes that successful MCP tool calls made while building, such as fetching sample data, use two tasks each, and that the AI tool doing the building may charge separately for its tokens.

The repair feature changed shortly before the billing details were published. A 4 November write-up on createwith describes how Next Gen Zaps can now diagnose a failure, test a repair and publish the fixed version automatically when the change is small. Larger changes, and any repair involving a login, still need a person to approve them. The same article reports a claim from Zapier's chief executive that the feature saved 100,000 tasks from failing in one week. Zapier hasn't published the method behind that figure, so we'd treat it as a vendor claim. The help guide confirms that troubleshooting with AI is switched on by default, that customers decide what the agent may change without approval, and that each applied fix becomes a new version in the workflow's history.

Why the billing date matters more than it looks

Most early access workflows were built while runs cost nothing, so few teams will have checked how many tasks those workflows actually consume. A Next Gen Zap that loops through every open invoice each morning, or calls a CRM once for every row in a spreadsheet, might have looked harmless in September and still produce a sizeable task bill in December. Zapier's documentation answers how runs are counted. How many runs your account produces is something only your own run history can tell you.

Classic Zaps aren't left untouched by any of this. Zapier's guide explains that importing a Classic Zap into the new format creates a copy, and the original keeps running unless someone turns it off. The guide also warns that leaving both versions on can cause duplicate runs. Any team that tested an import and forgot to switch off the Classic version could be paying for the same work twice once billing starts, and could also be sending duplicate emails, invoices or CRM updates today.

The repair agent raises a governance question as well as a cost one. An agent that rewrites a production workflow and publishes the new version is making a change to a business system. In an ITIL-style environment that change would normally be logged and someone would own it. Zapier sends an email after each fix and keeps the version history, which helps. Its guide also lists audit logs, templates and variables among the Enterprise features that are unsupported or unconfirmed for Next Gen Zaps during early access, and it advises against running the most sensitive workflows, such as legal, financial or private company files, through Next Gen Zaps until early access ends. Zapier hasn't said when early access will close, or whether billing starting on 1 December changes any of those limits.

What this means for NZ organisations

Zapier is common in small and mid-sized New Zealand businesses because it connects accounting, CRM and email tools without a developer. The cost of an automation now depends on three things: how the workflow was designed, how often it runs, and how much freedom the repair agent has. Under the Privacy Act 2020, a workflow that handles customer or staff information still needs an owner who knows what the workflow does with that data. An agent publishing its own fixes doesn't remove that responsibility from the business. Finance teams should also keep in mind that Zapier subscriptions are priced in US dollars, so higher task volumes add exchange rate exposure on top of the usage increase.

We'd treat the Next Gen Zaps billing date as a prompt to bring automation spending into normal operational review. Automations that grow without a clear owner tend to produce costs and errors that nobody can explain, and our process and automation work usually starts with an inventory of exactly that kind of sprawl.

Practical next steps before 1 December

• List every Next Gen Zap in your account, along with its owner, trigger, schedule and the systems it reads from or writes to.
• Estimate task use for each workflow using Zapier's counting rules, paying close attention to loops, agent data reads and code calls to external services.
• Check for imported Classic Zaps that are still running next to their Next Gen copies, and switch one of them off.
• Review the troubleshooting with AI settings and decide what the agent may change without approval. If a workflow touches finance or customer records, require approval for every change.
• Move any workflow handling sensitive financial, legal or personal data back to Classic Zaps, or another reviewed platform, until Zapier confirms audit log support.
• Record agent-published fixes in your change log, or at least have someone review Zapier's fix emails every week.
• Set a task usage alert or a monthly budget check so the first December invoice isn't a surprise.

For organisations weighing wider use of agents that change their own workflows, our AI consultancy team can help set the approval rules and ownership before those agents go live.