Starting December 1, 2026, at 12 pm ET (17:00 UTC), your Next Gen Zaps and Zapier SDK calls use tasks. Next Gen Zaps are free until then, and the free period ends for all customers at once.
An action costs the same number of tasks as in a Classic Zap, and a Next Gen Zap run uses tasks only for the actions and external calls that run in it. This article explains what uses tasks, what does not, and where to check your usage.
Starting December 1, 2026:
- Each app action and each external call uses 1 task.
- Each inbox-lease trigger in a Next Gen Zap's code uses 1 task. The trigger that starts the Next Gen Zap stays free.
- Each SDK action, external call, and inbox-lease trigger outside a Next Gen Zap uses 1 task.
- Most Classic Zaps are not affected. The exception is a Classic Zap with SDK calls in a Code by Zapier step.
What uses tasks in a Next Gen Zap
Next Gen Zaps use tasks at the same rates as Classic Zaps. Each app action uses 1 task, and specialized actions such as Lead Router and AI by Zapier have their own rates. Learn more about how task usage is measured in Zapier, and about the AI by Zapier model tier pricing.
Next Gen Zaps also use tasks for external calls. An external call is a request that your code makes to an API or URL through Zapier. It is the code version of an action. Each successful external call uses 1 task, whether or not it uses a connected account. Using a connected account lets Zapier handle sign-in for you, so you do not need API keys in your code.
You have a form that creates a contact in HubSpot, adds a row to Google Sheets, and posts in Slack.
| How it is built | What happens | Tasks used |
|---|---|---|
| Three app actions | The Zap runs a HubSpot action, a Google Sheets action, and a Slack action. | 3 tasks |
| Three external calls | The Zap's code reaches HubSpot, then Google Sheets, then Slack. | 3 tasks |
| Code that only reshapes data, such as formatting a name or a date | No action or external call runs. | No tasks |
While your MCP client, such as Claude, ChatGPT, Gemini, or Cursor, builds a Next Gen Zap, it may run app actions through Zapier MCP, such as fetching sample data. Each successful tool call uses tasks at the Zapier MCP rate.
Runs that use no tasks
If no action or external call that uses tasks runs, the run uses no tasks.
| Next Gen Zap | What happens in the run | Tasks used |
|---|---|---|
| A new Typeform lead creates a contact in HubSpot, then posts in the #sales Slack channel. | Two app actions run. | 2 tasks |
| A new Gmail email continues only if the subject contains "invoice". | The subject does not match, so the run stops before any action runs. | No tasks |
| A new Zapier Forms submission adds a record to a Zapier Table. | One action runs, but Zapier Tables is a free app, so the action uses no tasks. | No tasks |
SDK billing
The Zapier SDK is a toolkit that developers use in code to run actions in connected apps and to make external calls through Zapier. It does not have its own rates or separate billing. The location where the SDK runs determines how task usage is counted.
| Where the SDK runs | What uses tasks | Tasks used |
|---|---|---|
| Inside a Next Gen Zap | Each SDK external call and inbox-lease trigger | 1 task each. It counts as part of that Zap run and is not charged again as SDK usage. |
| Outside Zapier, such as on your own servers, in scripts, or in cron jobs | SDK actions, external calls, and inbox-lease triggers | 1 task each |
| Inside a Classic Code by Zapier step | SDK actions, external calls, and inbox-lease triggers | 1 task each, in addition to the step's base task |
Inside a Next Gen Zap, SDK usage is billed as part of that Zap. Outside Zapier, it is billed to your account directly.
SDK usage outside Zapier
| What | Tasks used |
|---|---|
| SDK action | 1 task for each action, the same price as in Next Gen Zaps and Classic Zaps |
| SDK inbox-lease trigger | 1 task for each trigger. Triggers that start a hosted Zap or Next Gen Zap stay free. |
| SDK external call | 1 task for each external call |
A batch or bulk call uses tasks for each item in the batch.
Only successful SDK calls use tasks. A failed SDK action, external call, or inbox-lease trigger does not use a task.
MCP calls do not have a separate SDK charge, and Sidekick has no billable SDK events currently.
What does not use tasks
In Next Gen Zaps and the SDK, the following do not use tasks:
- Anything that fails. A failed app action, external call, SDK action, or inbox-lease trigger does not use a task, the same as in Classic Zaps.
- The trigger that starts a hosted Zap or Next Gen Zap.
- Code that contacts a website or service directly, without going through Zapier.
- Code in a Next Gen Zap that does not contact an app.
- Checking a trigger inbox for new events. Only leasing an event to act on it uses a task. This is separate from the trigger of a hosted Zap or Next Gen Zap.
- Setup and lookup calls, such as listing connections or table fields.
- Composing, editing, testing, and publishing a Next Gen Zap.
Filters, formatting, loops, and branching do not use tasks, so a Next Gen Zap run that only does these things uses no tasks. Free By Zapier apps follow the same usage rules as in Classic Zaps.
A held run does not use tasks while it is held. Steps that finished before the hold use tasks as normal and are not charged again after you release the run. When you release the run, it continues from where it stopped, or starts if it was held before it began, and uses tasks for the steps it then runs.
Free apps and AI by Zapier pricing
Starting December 1, 2026, two changes make pricing consistent across Zapier:
- Free By Zapier apps, such as Zapier Tables, Zapier Forms, and Storage by Zapier, are free everywhere. They do not use tasks in Next Gen Zaps, through Zapier MCP, or through the SDK, whether you use them as an action or reach them through an external call (
fetch). - AI by Zapier uses its own price everywhere, including through Zapier MCP and the SDK. Until December 1, 2026, AI by Zapier does not use tasks through the SDK, and through Zapier MCP it uses only the Zapier MCP rate.
Where to check your usage
What you can check depends on where your automation runs.
| Where it runs | Task count for each run | Totals | Task History |
|---|---|---|---|
| Next Gen Zap | Not available | Usage Insights and your billing settings | Coming later |
| Classic Zap with SDK calls in a Code by Zapier step | Included in the Zap's usual task counts | Existing task usage pages, including Usage Insights | Available, the same as today |
| Outside Zapier, using the SDK | Not available | One account-level total, shown as SDK usage | Coming later |
For SDK usage outside Zapier, you can check how much you used in total, but not which script or job used it. Zapier does not provide a breakdown for each script or call.
All of this usage counts toward your plan's task limit and the emails Zapier sends when you reach 80% and 100% of your limit. If your account uses pay-per-task billing, this usage also counts toward your maximum pay-per-task usage. Learn more in How pay-per-task billing works in Zapier.
Next steps
You now know what uses tasks in Next Gen Zaps and the Zapier SDK, and when billing starts. Next:
- Check your current usage in Where to review your task usage in Zapier.
- Learn how Usage Insights works in Get usage insights for your Zap workflows.
- Learn how tasks are counted across Zapier in How is task usage measured in Zapier?.
- Use the SDK in a Classic Zap in Use the Zapier SDK in Code steps.
- Build your first Next Gen Zap in Get started with Next Gen Zaps.
- Get answers to your billing questions in Get help and support with Zapier.