Notion AI pricing in 2026: plans, credits and the Workers change

Notion credits are available only on Business and Enterprise. A Free or Plus workspace cannot simply buy credits to add Custom Agents or other credit-funded features. The full cost includes the eligible subscription as well as the credits. Workers start requiring credits on 15 October 2026, after their free beta period.

For a Plus team considering one automated workflow, the upgrade cost may matter more than the credits. First check which feature you need, then compare the workspace subscription and billing term before estimating usage.

Notion AI pricing in 2026: credits, plans and who can buy them

Disclosure: We make Breeze, which overlaps with Notion for project tracking. The plan and credit details below come from Notion's linked pricing and help pages, checked on 10 September 2026.

Contents

What do Notion's plans include?

The Notion pricing page separates a limited AI trial on Free and Plus from included AI features on Business and Enterprise. A trial is not an ongoing free allowance.

PlanUSD seat priceAI access
Free$0Limited Notion AI trial; credits unavailable
Plus$10 per member/month billed annually, or $12 monthlyLimited Notion AI trial; credits unavailable
Business$20 per member/month billed annually, or $24 monthlyIncluded AI features with applicable limits; credits available
EnterpriseCustom pricingAI and credit options under the plan's terms

The annual figures are monthly equivalents for a yearly subscription. Keep the billing term consistent when comparing seat and credit costs.

What do Notion credits cost?

Notion's credit documentation lists monthly credits at $10 per 1,000 and annual credits at $13 per 1,000. Monthly credits reset each month. Annual credits form a pool usable until the subscription renews; unused credits expire in both cases.

For self-service billing, the credit type follows the subscription: monthly plans buy monthly credits, and annual plans buy annual credits. Customers working with an account team have other purchase options. The higher annual price buys flexibility across the subscription year, so compare likely unused balances as well as the unit rate.

Credits fund Custom Agents, premium models and additional eligible AI usage. Workers join that billing model after the beta. Different features consume credits differently; a credit is not a promise of one completed task.

Can Free or Plus users buy Notion credits?

No. The Notion credits help page limits purchases to Business and Enterprise. Upgrading is therefore part of the cost for a Plus team that needs credit-funded features.

For ten members, moving from Plus to Business adds $100 a month at the annual-equivalent seat rates, before credits. On monthly billing, the difference is $120. Whether that is worthwhile depends on the work the feature will replace, not just the price of a credit pack.

What happens to Workers on 15 October 2026?

Workers run background code for tasks such as syncing data or writing updates. Notion's Workers pricing page says the Business and Enterprise beta is free to try, including Business trials, until credit billing begins on 15 October.

The published benchmark is about $0.0023 per run at the monthly credit rate, or roughly 4,348 runs per 1,000 credits. Actual consumption varies with runtime and processing. At that benchmark, 10,000 runs would use about 2,300 credits, worth $23 at the monthly rate or $29.90 at the annual-credit rate. These are usage estimates, not fixed quotes.

Review the runs and estimated credits for your own Worker before the beta ends. A scheduled sync, an event-driven update and a tool called by an agent can run at very different frequencies.

What would a ten-person team budget?

These examples use monthly seat billing and chosen monthly credit budgets. They show the arithmetic, not how many agents a given budget will support.

SetupSeats per monthChosen credit budgetMonthly total
Plus, no credit-funded features10 × $12 = $120Unavailable$120
Business with 1,000 monthly credits10 × $24 = $240$10$250
Business with 5,000 monthly credits10 × $24 = $240$50$290

For annual billing, ten Business seats cost $2,400 a year at the listed rate. A chosen annual pool of 12,000 credits would add $156, for $2,556 before tax. That pool could run out sooner or later than twelve months depending on actual use; it is not an included allowance.

Before choosing a budget, test one representative workflow. Record what triggers it, how often it runs and which features it calls. A description such as "one agent" is not enough to estimate its consumption.

What happens when the allowance or credits run out?

These are two different limits. Notion's AI allowance documentation describes six-hour and monthly windows for certain Business and Enterprise features. It does not publish a numerical included allowance. When a limit is reached, affected features can pause until it refreshes, or use credits if an admin enables that option. Custom Agents, Workers and premium models sit outside that allowance.

If the workspace lacks credits, Custom Agents and premium models pause. Notion sends admins in-app and email notifications at 80% and 100% credit usage. Assign someone to review those alerts if a workflow supports important work.

Do not assume a pause is harmless just because the rest of the workspace remains available. For an intake or status-update workflow, keep a way to identify work that did not run and handle it while the feature is paused.

How do you estimate the cost of one workflow?

Start with a task you can describe without mentioning an agent: copy approved requests into a project database, summarise a weekly intake queue, or update records when a source changes. That description gives you something concrete to test and a way to tell whether the automation has finished correctly.

Next, count the opportunities for it to run. A weekly summary has a predictable schedule. An update triggered by every changed record depends on how often people edit the source. Include reruns, test runs and any follow-up steps in the estimate rather than counting only successful final outputs.

Measure a small sample with realistic inputs. Record the credits used, whether the result needed correction and how long a person spent reviewing it. An inexpensive run is not necessarily a useful one if someone must redo the work afterward. Equally, a higher-cost run may be worthwhile if it reliably replaces a substantial recurring task.

Keep Workers and AI reasoning distinct in that test. A Worker can run code without every step being an AI request. If the wider workflow also calls a Custom Agent or premium model, review that consumption separately. Do not apply the published Worker benchmark to the complete workflow without checking what else runs.

How should you compare monthly and annual credit budgets?

The monthly rate is lower per credit, but unused monthly credits expire at the reset. An annual pool gives you more flexibility across busy and quiet periods. The better fit depends on when work happens as well as how much work happens.

For example, a team processing a similar number of requests each week can estimate a recurring monthly budget from a representative sample. A team preparing several large launches may use little for weeks, then much more in a short period. Annual pooling may fit that pattern, but it still requires an estimate of total consumption before renewal.

Keep the purchase rules in view: a self-service annual workspace cannot simply use the cheaper monthly credit rate in its budget. Compare an annual subscription with annual credits, or a monthly subscription with monthly credits. If an account team offers different terms, calculate from that offer.

Before buying a larger pool, decide who will review usage and how often. Check whether unused workflows are still running and whether a change to a prompt or trigger altered consumption. Revisit the estimate after a meaningful workflow change rather than assuming the original test remains representative.

The useful outcome is a budget tied to a known amount of work and an acceptable result. A generic allocation for “AI” makes it harder to decide whether more credits would solve a real bottleneck or simply fund more runs.

Should a Plus team upgrade for an agent?

Compare the complete upgrade with a specific task. An agent that saves hours of recurring work may justify the cost. An occasional convenience may not.

  • Upgrade when the workflow earns its cost. Test the output and account for the whole workspace, credits and any review the result still needs.
  • Stay on Plus if you do not need the paid AI. Evaluate Plus for its core workspace features; do not plan around permanent access to a limited trial.
  • Compare the underlying job. If the aim is project coordination, consider whether a simpler workflow would meet the need. If it involves data across several systems, an automation may still be useful.

The Notion alternatives comparison can help when the issue is product fit. Switching tools also takes time, so compare that effort with keeping the workflow in Notion.

Choose the subscription before sizing the credits

Start with the feature, confirm the eligible plan and billing term, then measure a realistic workload. For Workers, use the beta to estimate consumption before 15 October. That gives you a budget based on what the team will run rather than a generic promise about what AI might save.