目錄
The information in this article is current as of September 2026. Workers are still in beta, and the billing date and rates may still change.
A very practical discussion appeared on r/Notion with a title that asked directly: “Do Agents look 10 times more expensive than Workers?” The poster had converted many Make.com scenarios into Notion Workers and observed that a single Worker Run consumed about 0.2–0.6 credits. When they tested a Custom Agent on a workflow that did nothing more than change a Property Status, however, one run used about 2.5 credits. In that single test, the difference was roughly 4–12.5 times, so it is easy to come away with the initial impression that Agents cost far more.
More importantly, Workers are still in a free beta. A newer Notion Help Center page says that Workers will officially begin consuming Notion credits on October 15, 2026. During the beta, Business, Enterprise, and Business Trial workspaces can see estimated Credits Usage and use real workflows to calculate how many credits they may need later. Some older English release pages still show the previous date of August 11, so it is worth checking the Billing section in the Workspace and the latest Help Center again before billing officially begins.
What really needs to be reconsidered is not simply that “Agents are too expensive.” Although all of them are called automation, Notion now separates automation into three completely different tools: Database Automations handle explicit conditions and actions, Workers execute predictable program logic, and Custom Agents handle work that requires reading Context, making judgments, and deciding what to do next. Putting these three tools in the wrong place not only raises costs but can also make a workflow harder to maintain than it was before.
How Much Does One Notion Worker Run Cost Compared With a Custom Agent Run?
A Worker Usually Costs About 0.23 Credit per Run, but That Is Not a Fixed Rate
Notion’s current Worker Benchmark is typically about US$0.0023 per Run. Because 1,000 Notion credits cost US$10, each credit is equivalent to US$0.01. A typical Worker Run therefore consumes about 0.23 credit, and 1,000 credits can support roughly 4,348 typical Runs.
This figure is close to the 0.2–0.6 credits observed by the Reddit poster, but 0.23 should not be treated as a fixed unit price. Actual Worker usage still depends on runtime, processing volume, and the work being performed. Notion itself uses the wording typically cost; it does not guarantee that every execution will deduct exactly 0.23 credit.
It is also important to understand the Worker billing unit. Each Scheduled Sync execution counts as one Run, while each Event processed by a Webhook counts as one. If a Custom Agent uses a Worker as a Tool, each Tool Call counts as a separate Worker Run. An Agent Run that calls a Worker four times will therefore incur the Agent’s own Credits plus four Worker Runs.
Custom Agents Now Have Official Cost Ranges, So There Is No Need to Guess
The statement in the original draft that “Agents have no official rates and can only be estimated through third parties” no longer applies. Notion now publishes real Benchmarks for several common types of Custom Agents:
| Custom Agent Type | Official Estimated Cost per Run | Approximate Credits Used | Approximate Runs per 1,000 Credits |
| Q&A Agent | US$0.03–0.11 | 3–11 | 90–333 Runs |
| Task Routing | US$0.05–0.15 | 5–15 | 65–190 Runs |
| Status Update | US$0.08–0.18 | 8–18 | 57–133 Runs |
| Mail Triage | US$0.04–0.10 | 4–10 | 100–250 Runs |
| Daily Brief | US$0.10–0.30 | 10–30 | 33–100 Runs |
The cost of the same Agent also varies with the amount of content it reads, the number of databases it searches, the number of Tool Calls, execution frequency, and Model Choice. These figures are therefore estimated ranges rather than fixed prices.
If the typical official Worker cost of 0.23 credit is compared loosely with the official Custom Agent range of 3–30 credits, the difference can indeed reach dozens or even more than one hundred times. However, this is still not a fair comparison of the “same job.” The Agents in Notion’s examples read Context, make decisions, create data, or send messages, while the Worker Benchmark mainly covers the execution of fixed code.
The Reddit statement that “Agents cost 10 times more than Workers” can therefore be treated as one person’s real-world test, but it cannot be elevated into a fixed pricing rule for the product.
Why Do Custom Agents Usually Cost Much More Than Workers?
A Custom Agent Spends Credits on Judgment; a Worker Spends Them on Execution
Workers run code. The logic for syncing Salesforce, receiving a Webhook, or updating Notion after a calculation has already been written by a developer, so the Runtime only needs to follow the predefined process. Notion also positions Workers for tasks that do not require AI Reasoning, such as Syncing Data, Writing Updates, and Handling Events.
A Custom Agent faces a different kind of problem. It might read a Slack Message, search several Databases, classify the content, identify the Owner, set the Priority, create a Task, and then notify the people involved. The more data it reads, the more steps it takes, and the more powerful the model it uses, the more Credits it consumes.
“An Agent thinks while a Worker acts” works as a simplified explanation, but a Worker is not devoid of logic; it can execute highly complex programs. The real distinction is whether the decision logic has been fixed in advance. A Worker executes Deterministic Logic defined by a developer, while a Custom Agent uses a model to decide how to complete a task based on the current Context.
If a workflow performs the same API Calls, field transformations, and status updates every day, there is no reason to pay the model to “think it through” again every time.
Notion Already Recommends Letting Agents Decide and Workers Execute
The Two Tools Are Not Competitors; Notion Recommends Using Them Together
Notion’s official Workers documentation explicitly describes a common arrangement in which a Custom Agent decides what to do and a Worker reliably executes specific steps.
For example, when a customer sends an Email, deciding whether it is a refund request, Bug, partnership proposal, or general inquiry is difficult to cover fully with fixed conditions and is better suited to an Agent. Once that decision is made, if the remaining work is simply to create a Task in a fixed format, populate a few fields, and call a predefined API according to the category, the second half can be handed to a Worker.
Besides saving Credits, this arrangement has another practical advantage: deterministic work is easier to Debug. If the Agent makes the wrong decision, its Instructions can be adjusted. If a Worker API Call fails, the Error can be examined in the Logs. When everything is packed into one Agent Run, the result may show high Credits without making it easy to identify which steps truly required a model.
Which Notion Automations Do Not Need an Agent at All?
Layer One: If the Rules Are Clear, Start With Database Automation or a Formula
If the requirement is simply to change another Property after Status becomes complete, assign an owner when a new Page is created, create content on a schedule, or send a notification, Notion Database Automations can already handle many cases. Paid plans can create Database Automations, while the Free Plan can create only certain limited actions, such as a Slack Notification. Formula and Button can also handle many forms of fixed logic that do not require background execution.
Ordinary Database Automations do not use the Notion credits billing system for Workers and Custom Agents. If native Automation can already do the job, there is no need to rewrite the same condition as an Agent Prompt.
For example, there is no advantage in either cost or reliability to making a model reread the Context and decide whether to enter a date every time a workflow needs to perform “Status changes to Published → fill Published Date with today.”
Layer Two: If Code Execution Is Needed but the Rules Are Fixed, Consider a Worker
A workflow enters Worker territory when it needs external APIs, cross-system synchronization, Webhooks, batch data processing, or more complex transformation logic. Workers currently focus on Database Sync, Custom Agent Tools, and Webhook Triggers. They also run on Notion’s own Infrastructure, so there is no need to maintain a separate Lambda or other Server.
Common examples include regularly syncing an external CRM, updating a Billing Database after receiving a Stripe Webhook, batch-cleaning data, calling an API according to predefined Rules, and giving a Custom Agent a fixed calculation or lookup Tool.
The original draft’s statement that “if it can be written as one if-then sentence, it should not use an Agent” points in the right direction but is slightly too absolute. Some logic can be expressed as if-then rules, yet the number of conditions and exceptions may make it not worth maintaining manually. A better question is: Can the rules be defined completely and reliably in advance? If so, start with Automation or a Worker. If the input itself is ambiguous, then move to an Agent.
Layer Three: Use a Custom Agent When Understanding and Trade-Offs Are Required
Classifying a customer Email, deciding which meeting items are genuinely unresolved, identifying which message shows partnership intent, or choosing which competitor updates belong in a weekly report cannot be handled by one fixed Formula and requires different Context for each decision.
These are the situations that better match the purpose of a Custom Agent. Notion also recommends narrowing the Scope, making the Trigger specific, granting Context access only to the Pages and Databases that are actually needed, and using lighter models for simpler work. These adjustments can reduce both mistakes and Credit Usage.
Custom Agent Costs Have Already Fallen Once, So Why Are They Still Higher Than Worker Costs?
On April 14, Notion announced that it had reduced Custom Agent execution costs by about 35%–50% overall, particularly for recurring tasks such as Mail Triage. It also added lower-credit model options including GPT-5.4 Mini/Nano, Haiku 4.5, and MiniMax M2.5. Some models can use up to about 10 times fewer Credits than higher-end models.
This means Notion has not ignored Agent Cost. Model inference is simply more expensive than fixed Code Execution. The purpose of a Worker is to remove the parts that do not need AI Decision-making and execute them at a more predictable price.
Architecture optimization therefore does not mean “replace every Agent with a Worker.” It means identifying which steps in an Agent Run never needed AI in the first place.
What Should Be Understood About Notion Credits Before October 15?
Monthly Credits Reset, and Unused Credits Do Not Accumulate
Notion credits are shared across a Workspace, and Business and Enterprise plans can purchase more. The current standard price is US$10 per 1,000 credits. Monthly Credits reset during each Billing Period, and unused credits do not Roll Over into the next one.
When purchasing Credits, it is more reasonable to observe actual usage for one or two Billing Cycles than to buy a large amount immediately. Notion also recommends starting an Agent with a small Scope, running it for a while, and adjusting it according to real Usage in the Dashboard.
Custom Agents Pause When Credits Run Out, but Automatic Top-Ups Can Be Configured
If a Workspace does not have enough Notion credits, Custom Agents pause by default until the next Billing Cycle resets or an administrator adds more Credits. If a Task that is already running encounters the Cap, the system may allow that Run to finish before preventing new work from starting.
This does not mean every Workspace will suddenly stop. Notion also offers Auto Adjust, which lets an administrator automatically increase the credit allocation and Spending Cap when Credits approach the limit, reducing the chance that an Agent will be interrupted. Multi-Workspace Enterprise Contracts also have On-demand Spend.
No official documentation was found to support the original draft’s statement that “missed schedules will not run retroactively after credits are added,” so it is not recommended to retain it. For critical workflows, Activity and Insights should be monitored separately to verify that every expected Run actually completed, rather than assuming that the system will always make up missed Runs after Credits return—or that it never will.
Credits Are Shared Across the Workspace, but Each Agent Can Have Its Own Limit
All Custom Agents draw from the same Workspace Credit Balance, so one high-frequency Agent can quickly increase total Spend. Administrators can now set a Credit Limit for each Custom Agent, automatically Pause an Agent when it reaches the Threshold, and restrict which Members are allowed to create Agents.
What a team really needs, then, is not daily surveillance of everyone. It should set limits for Agents that are likely to trigger frequently, then use the Dashboard to identify what is actually consuming the most Credits.
How Can Notion Automation Costs Be Audited Before October 15?
Establish a Real Baseline in the Credits Dashboard Instead of Relying Only on Estimates
Estimated Credit Usage is already visible during the free Workers beta, and the Dashboard shows Runs Completed, Credits Used, Creator, and Status. Note that Worker Spend is separate from Custom Agent Spend by default and may not appear in the main Usage Chart at the top. To compare them together, enable Include Worker spend.
Rather than assuming in advance that “every Worker costs 0.23 credits,” it is more useful to run the Workflows that are actually in production for a period and review the average Credits per Run for each one.
Before the beta ends, it can also make sense to complete known one-time bulk synchronizations or Backfills. The main purpose, however, should be to measure real Runtime and Credits at the same time—not to run unnecessary processes at scale simply because they are currently free.
Divide Existing Workflows Into Automation, Worker, and Agent
Only two questions are needed during an audit. First, can the rules be written clearly in advance? Second, does a model need to choose based on Context?
For completely fixed Property Updates, Notifications, and Page Creation, start with Database Automation. Work that requires Code, APIs, or high-volume data transformation but remains predictable belongs in a Worker. Only work that requires reading text, interpreting meaning, making trade-offs, or deciding the next Action should remain with a Custom Agent.
If only 20% of an Agent workflow truly requires a model, keep that 20% in the Agent and let a Worker take over the deterministic operations that follow. This is exactly the combined pattern described in the official Workers documentation.
Triggers Can Make a Bill Spiral Faster Than Prompts
The total cost of a Custom Agent depends not only on the cost of each Run but also on Trigger frequency. Notion recommends avoiding broad triggers such as “any Message” or “any Database Update” and narrowing them to a specific @mention, a particular Property Change, or an Event that genuinely needs processing.
The effect is even clearer with Workers. Notion estimates that a typical Sync running once a day costs about US$0.07 per month. Running it once an hour costs about US$1.66, while running it every 15 minutes increases the amount to about US$6.62. What drives costs up is often not the program itself but the fact that it runs far more frequently than necessary.
Model Choice Directly Affects Custom Agent Credits
A Custom Agent can use Auto or a specified model, and higher-end models require more Credits. Notion still recommends using Auto for most work, or assigning a lighter model to simpler, tightly scoped Sub-agents while reserving stronger models for genuinely complex steps.
Instead of fixing every Agent to the most powerful model, reviewing which models, Tool Calls, and Steps were actually used in Insights usually makes it easier to find wasted spending.
Will Free and Plus Users Be Affected by Worker Billing?
Workers Are Already Limited to Business and Enterprise
Workers are currently available only on Business and Enterprise, so Free and Plus users will not suddenly receive a Worker Credits bill on October 15. Those two plans also cannot purchase Notion credits directly to use Workers or Custom Agents.
The original draft’s statement that both Free and Plus users can rely on Database Automations for personal workflows also needs to be separated by plan. Plus can create ordinary Database Automations, while Free can create only limited types, such as Slack Notification Automations. Other Automations can mainly be used through existing Templates and cannot be edited by the user. Features such as Formula and Buttons can still handle many simple forms of logic.
For Plus users, it therefore makes sense to push native Automation as far as possible. Free users who need true background automation should evaluate an external tool or a plan upgrade instead of assuming that all Automations can be created for free.
Before Workers Start Charging, Decide Again Which Steps Actually Need AI
The calculation in the Reddit post saying that an “Agent looks 10 times more expensive than a Worker” was not wrong, but it represented only one specific test: a Worker consumed about 0.2–0.6 credits, while using an Agent for a very simple Status Update consumed about 2.5 credits.
Notion’s current official Benchmarks show the real scale more clearly. A Worker Run typically costs only about 0.23 credit, while a Custom Agent can cost anywhere from a few credits to dozens depending on the task. There is no mysterious reason for the gap. The former executes code that has already been written; the latter has to read Context, select tools, reason, and decide what to do next.
The most useful task before October billing is therefore not to rush to convert every Agent into a Worker, but to break down every workflow. Keep anything that can be handled by a Formula or Database Automation in the native layer. Give stable program logic to a Worker. Pay the Agent’s reasoning cost only for the small portion that truly requires judgment.
The Credits Dashboard becomes genuinely useful only after these three layers have been separated. Otherwise, seeing that an Agent is expensive does not reveal whether the wrong model was used, the Trigger was too broad, too much Context was read, or the task never needed an Agent in the first place.
FAQs
No. Notion says a Worker typically costs about US$0.0023 per Run, or roughly 0.23 credit, but actual Credits vary with runtime and processing volume.
Notion’s current typical examples range from about 3 to 30 credits per Run. A Q&A Agent uses about 3–11, Mail Triage 4–10, Status Update 8–18, and Daily Brief 10–30 credits. Actual usage still depends on data volume, Steps, Tool Calls, frequency, and model.
There is no fixed 10-times ratio. The Reddit example was roughly 4–12.5 times, while a loose comparison between Notion’s typical Worker and its different Agent Use Cases can produce a difference of dozens to over one hundred times. The tools perform different kinds of work, so this ratio is not a fixed price difference.
If there are not enough Credits, Custom Agents pause until the next cycle resets or an administrator adds more. Administrators can also enable Auto Adjust to purchase additional Credits near the limit and reduce the chance that a workflow will stop unexpectedly.
Ordinary Monthly Notion credits do not Roll Over. The purchased monthly allocation is provided again when the new Billing Cycle begins.
Not currently. Workers are available only on Business and Enterprise. Developer Mode can be enabled on every plan, but that does not mean all Developer Platform features are available.
A Worker should usually be considered first when the rules can be fully defined in advance and a model does not need to interpret meaning—for example, data synchronization, Webhooks, batch updates, and fixed API workflows. A Custom Agent is better when text must be understood, Context evaluated, or the next step decided.
As of September 2, 2026, a newer Notion Help Center page says Workers will begin using Notion credits on October 15, 2026. Business, Enterprise, and Business Trial are still in a free beta. Some older English pages retain the previous August 11 date, so check the latest Help Center and Workspace Billing before official charging begins.