What changed
Starting August 11, 2026, Notion Workers moved from a free beta to Notion-credit billing on Business and Enterprise plans. Notion says Workers typically cost about $0.0023 per run, equivalent to roughly 4,348 runs for 1,000 monthly Notion credits ($10). Scheduled sync executions, agent-triggered Worker tool calls and handled webhook events each count as runs, although actual credit use can vary with runtime and processing work.
Why it matters
Workers turn Notion from a document/workspace product into a place where teams can run integration code, sync external systems and expose tools to Custom Agents. Once those executions are metered, workflow architecture becomes part of SaaS spend: an every-minute sync, a high-volume webhook or an agent that calls several Worker tools per task can scale costs very differently from a daily batch. For builders, the practical question is no longer just whether Notion can host the automation, but whether its execution frequency and event volume fit the credit budget.
One run is the core billing unit
Notion counts each scheduled sync execution, each Worker tool call triggered by a Custom Agent and each webhook event handled by a Worker as a run. A typical run is priced around $0.0023, but Notion says actual credit consumption can vary based on how long the Worker runs and how much processing it performs.
Frequency can dominate cost
Because every scheduled execution is billable, sync cadence matters directly. Notion’s own examples put a daily sync at pennies per month, hourly at around $1.66, and every 15 minutes at around $6.62 for a representative Worker. The same logic applies to event-driven traffic: high-volume webhook streams scale nearly linearly with handled events.
Agent workflows can multiply Worker runs
A single Custom Agent run can invoke a Worker multiple times. Notion’s examples explicitly model several Worker tool calls per agent run, meaning builders need to budget both the Custom Agent’s own credit usage and the additional Worker runs it triggers. Tool design and batching can therefore affect total agent economics even when the Worker code itself is simple.
Usage visibility is part of the rollout
Admins and Worker creators can inspect Worker usage in the Notion credits dashboard and CLI. Notion recommends starting with slower schedules, batching work, limiting replicated data and avoiding runaway retries. Those recommendations effectively define the first set of cost-control levers available to teams using Workers in production.