> ## Content Index
> Fetch the complete content index at: https://www.doitwithfriday.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Zapier Next Gen Zaps Start Using Tasks Dec 1: What to Count
- URL: https://www.doitwithfriday.com/news/zapier-next-gen-zaps-billing-december-1/
- Published: 2026-11-21T10:24:30.000Z
- Updated: 2026-11-21T12:40:55.000Z
- Description: From December 1 at 12 pm ET, every app action and every external call in a Next Gen Zap uses one task. Count them per run now, before the free period ends.
- Author: Kevin Anderson
- Tags: News, What It Costs

Next Gen Zaps, which you or an AI agent can build in the editor, in chat or in code, have run free in early access. That ends December 1, 2026, at 12 pm ET.

In Friday's view, if you built these Zaps in the free period, count the app actions and external calls per run now and check the total against your task limit.

## Zapier starts billing Next Gen Zaps on December 1

Zapier has set one date and one time for the change. It covers Next Gen Zaps and calls made through the Zapier SDK, and it reaches every customer at the same moment, with no rollout by plan.

### The date, the time and who it covers

[Zapier's help article on how these Zaps and the SDK are billed](https://help.zapier.com/hc/en-us/articles/49965546559117?ref=doitwithfriday.com) opens with the rule: "Starting December 1, 2026, at 12 pm ET (17:00 UTC), your Next Gen Zaps and Zapier SDK calls use tasks." It adds that they "are free until then, and the free period ends for all customers at once."

The product page says the same in its FAQ: "Billing for Next Gen Zaps starts December 1, 2026." The same FAQ describes early access as free on any paid Zapier plan, with "No task usage, no billing, no surprises."

### What Zapier says is not changing

The product FAQ says Next Gen Zaps "use the same task-based pricing as the rest of Zapier, and the published price list is unchanged." On Zapier's US pricing page, read on November 21 with yearly billing selected by default, Professional starts from $19.99 a month and Team from $69 a month, in USD.

Classic Zaps stay as they are, with one exception. The help article says: "Most Classic Zaps are not affected. The exception is a Classic Zap with SDK calls in a Code by Zapier step." If your builder put Zapier SDK calls inside a Code by Zapier step, that Classic Zap uses tasks for those calls from December 1.

## What uses tasks in a Next Gen Zap

The help article's rule is that a run uses tasks only for the actions and external calls that run in it. The table lists what the help article says each kind of step uses from December 1, 2026.

| Step in a Next Gen Zap                                                         | Tasks used                                                                      |
| ------------------------------------------------------------------------------ | ------------------------------------------------------------------------------- |
| The trigger that starts the Zap                                                | 0                                                                               |
| Each app action, such as sending a Slack message                               | 1, the same as in a Classic Zap                                                 |
| Each successful external call through Zapier                                   | 1                                                                               |
| Each inbox-lease trigger in the Zap's code                                     | 1                                                                               |
| Specialized actions such as Lead Router and AI by Zapier                       | Their own rates                                                                 |
| Filters, formatting, loops and branching                                       | 0                                                                               |
| Free By Zapier apps, such as Zapier Tables, Zapier Forms and Storage by Zapier | 0                                                                               |
| Anything that fails                                                            | 0                                                                               |
| Composing, editing, testing and publishing the Zap                             | 0, except app actions an MCP client runs while building, at the Zapier MCP rate |

### External calls are the new line item

Zapier defines the new item plainly: "An external call is a request that your code makes to an API or URL through Zapier." It calls this the code version of an action: "Each successful external call uses 1 task, whether or not it uses a connected account."

The FAQ puts it in the reader's terms: the one new line item "is the external call your agent uses to read data from an app, at one task per call." This is where an agent-built Zap can use more tasks than its owner expects. An agent writing code looks things up: a customer record, an order, a product price. Each lookup through Zapier counts, and a loop that makes one external call per item uses one task per item.

### What runs free

The help article lists code that contacts a website or service directly, without going through Zapier, as free, along with code that does not contact an app. The product FAQ puts it more broadly: "Each call your code makes to an outside service counts as one task." Keep a separate count of direct calls so you can check either reading. Setup and lookup calls, such as listing connections or table fields, are free. A held run uses no tasks while it is held. Zapier also says that from December 1, Free By Zapier apps "are free everywhere," including through Zapier MCP and through the Zapier SDK.

Two items have their own prices. AI by Zapier "uses its own price everywhere" from December 1\. And while an MCP client such as Claude, ChatGPT, Gemini or Cursor builds one of these Zaps, any app action it runs through Zapier MCP, such as fetching sample data, uses tasks at the Zapier MCP rate.

### The Zapier SDK outside a Next Gen Zap

Zapier describes the Zapier SDK as a toolkit developers use in code to run actions and make external calls through Zapier, and it has no separate billing. Inside a Next Gen Zap, SDK calls count as part of that run and are not charged again as SDK usage. Outside Zapier, on your own servers, in scripts or in cron jobs, each SDK action, external call and inbox-lease trigger uses 1 task, and a batch call uses tasks for each item in it.

Zapier shows Zapier SDK usage outside Zapier as one account-level total, and it says it "does not provide a breakdown for each script or call." If a developer runs scripts against your account, ask for a list of them before December 1.

## Two Zapier pages disagree on the minimum per run

Zapier's help article and its product FAQ, both read on November 21, give different answers for a run in which no app action or external call runs, such as a run that only filters and formats.

![Zapier FAQ, Will Next Gen Zaps cost more than my current Zaps: the rate per action is the same, and, highlighted, from December 1, 2026 a completed Next Gen Zap run counts at least 1 task. Below, Zapier help: if no action or external call that uses tasks runs, the run uses no tasks.](https://storage.ghost.io/c/67/23/6723d566-f4a4-4c03-8b45-4f8f0948342b/content/images/2026/11/zapier-next-gen-zaps-task-rule.webp)

The Next Gen Zaps FAQ and the Help Center article give different rules for a run with no task-using step, in Zapier's own words. Source: Zapier, zapier.com/workflows FAQ and How Next Gen Zaps and the Zapier SDK are billed, checked Nov 21, 2026.

### The help article: no task-using step, no tasks

[The help article](https://help.zapier.com/hc/en-us/articles/49965546559117?ref=doitwithfriday.com) has a section titled "Runs that use no tasks." Its rule is one sentence: "If no action or external call that uses tasks runs, the run uses no tasks." It repeats the point later: filters, formatting, loops and branching do not use tasks, "so a Next Gen Zap run that only does these things uses no tasks." On that reading, a run that stops at a filter costs nothing.

### The product FAQ: at least 1 task per completed run

The FAQ on [zapier.com/workflows](https://zapier.com/workflows?ref=doitwithfriday.com) answers the question "Will Next Gen Zaps cost more than my current Zaps?" with a different rule: "One thing is new from December 1, 2026: a completed Next Gen Zap run counts at least 1 task." On that reading, a run that finishes with only free steps counts 1 task. For a Zap that fires 500 times a month and finishes 300 of those runs without an app action or external call, the gap between the two readings is 300 tasks a month.

### How to check your own count

The help article's usage table says a task count for each run is "Not available" for these Zaps, and Task History is "Coming later." What you can see are totals, in Usage Insights and in your billing settings.

In Friday's view, the practical test is to note your account's task total before 12 pm ET on December 1, let your filter-heavy Zaps run for a day, and compare the change with what the help article's rules predict. If the total rises by one task per filtered run, the FAQ's rule is the one being applied, and you can ask Zapier support which page to rely on.

## Count your Next Gen Zaps against your task limit before December 1

This usage draws on the same pool as your other Zaps. Zapier's pricing page says tasks are shared across your account, so one busy agent-built Zap can use up the task limit your other Zaps need.

### A worked example: a bakery's order follow-up Zap

For example, a bakery with two shops and an online store uses a Next Gen Zap, built by an agent, for its online orders. When an order arrives, the Zap reads the customer's record in the CRM, checks each item against the bakery's inventory app with one external call per item, sends a confirmation email as an app action, and adds a row to a Google Sheets order log as a second app action. A branch skips the inventory check for gift cards.

Under the help article's rules, the trigger is free, the branch is free, the CRM lookup is 1 task, the confirmation and the log row are 1 task each, and an order with three items adds 3 tasks for the inventory checks. That is 6 tasks for a three-item order. At about 400 online orders a month, averaging three items, the Zap uses about 2,400 tasks a month.

Zapier's pricing page lists task tiers that include 2,000 and 5,000 tasks a month, so this one Zap alone goes past a 2,000-task limit before the bakery's Classic Zaps draw on the same pool. If the bakery replaced the per-item inventory checks with one external call that returns stock for the whole order, the same run would drop to 4 tasks, about 1,600 a month. A batch or bulk call does not get that saving: Zapier bills it per item.

### What happens when you reach the task limit

The help article says this usage "counts toward your plan's task limit and the emails Zapier sends when you reach 80% and 100% of your limit." Zapier's pricing page adds: "Pick any task tier, and if you reach your limit, you'll be switched to pay-as-you-go unless you turn it off or move up to a higher tier."

For accounts on pay-per-task billing, the help article says this usage "also counts toward your maximum pay-per-task usage." Check which setting your account has before December 1, so a busy week does not turn into an overage you did not plan for.

## Friday's view on agent-built Zaps and the meter

The billing change is reasonable: an agent-built Zap that reads data from five apps per run does more work than a two-step Zap. The risk is in how these Zaps were built.

### Why an agent-built Zap needs a count

An agent working toward a Zap that runs has no reason to keep external calls low unless you ask it to. Ask the agent to rewrite its lookups as fewer requests, not batch calls, and tell it that each call uses a task.

### Three things to keep in the owner's hands

First, a list of every Next Gen Zap on the account, with its runs per month and its tasks per run, written down before December 1\. Second, a rule for builders, human or agent, that lookups go in one request where the app's API allows it, since a batch call still uses a task per item, and that free steps such as filters and Zapier Tables come first. Third, a named person who checks the account's task total each week until Task History arrives. If you are still choosing a platform for this kind of work, our [comparison of n8n, Zapier and Make](https://www.doitwithfriday.com/blog/n8n-vs-zapier-vs-make/) sets the three side by side.

If you want the per-run count and a design that fits your task limit done for your account, [our workflow automation service](https://www.doitwithfriday.com/services/workflows/) covers that kind of work.

## Before December 1 at 12 pm ET

From December 1, 2026, at 12 pm ET, each app action and each external call in a Next Gen Zap uses 1 task, and Zapier's two pages disagree on runs with no task-using step.

Before the meter starts, list your Next Gen Zaps, count the app actions and external calls in a typical run, multiply by monthly runs, and add the total to your Classic Zaps' usage. Then compare it with your task tier and check your pay-as-you-go setting. If you want a second pair of eyes on the count, [send us the list of Zaps you plan to keep running](https://www.doitwithfriday.com/contact/).

Last checked: November 21, 2026, against Zapier's help article on how Next Gen Zaps and the Zapier SDK are billed, the Next Gen Zaps FAQ on zapier.com/workflows and Zapier's US pricing page.

Billing rules and prices come from Zapier's help article, its Next Gen Zaps product page and its US pricing page, the primary sources, checked November 21, 2026\. Next Gen Zaps are in early access and the billing rules can change. Friday has no relationship with Zapier. Statements marked as Friday's view are opinion.