# Notion Workers now have a per-run cost model inside Notion credits Notion’s hosted code runtime stopped being free on August 11. Workers now consume Notion credits, typically about $0.0023 per run, turning sync frequency, webhook volume and agent-triggered tool calls into explicit operating costs. Notion Workers are now metered inside the same credits system as Custom Agents. The important builder shift is that schedules, webhook fan-out and agent tool-call counts now directly affect cost. - Status: Active - Published: 2026-08-22T15:25:27+12:00 - Updated: 2026-08-22T15:25:27+12:00 - Categories: Web Development, SaaS, Pricing & Billing, SaaS Operations, Developer Tools - Tags: developer platforms, Notion, Notion Workers, usage pricing - Canonical HTML: https://beyondthe.news/dossiers/notion-workers-credits-per-run-pricing-august-2026 ## 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. ## Key details - Worker billing started August 11, 2026. - Workers are available on Business and Enterprise plans. - A typical Worker run costs about $0.0023 according to Notion’s current help documentation. - Roughly 4,348 typical runs correspond to 1,000 Notion credits ($10). - Scheduled syncs, agent-triggered tool calls and handled webhook events each count as Worker runs. - Actual credit use can vary with runtime and processing needs. - Worker usage is visible through the Notion credits dashboard and CLI. ## Builder takeaways - Calculate monthly run volume from schedule frequency, webhook event rate and average Worker calls per agent task before moving an automation into Notion. - Batch small changes when possible; one batched execution can be cheaper than firing a Worker for every low-value event. - Add retry caps and failure monitoring so a broken integration does not turn into repeated billable runs. - Budget Custom Agent and Worker usage separately when agents invoke Worker tools—the agent decision and the code execution consume different credits. - Use the dashboard and CLI after workflow changes to compare estimated versus actual run consumption rather than relying only on Notion’s benchmark rate. ## What to watch - Whether Notion changes the typical per-run benchmark as Workers leave beta. - When spend limits become available specifically for Workers rather than only usage visibility. - Whether additional trigger types or longer-running workloads change the credit model materially. - Whether Notion adds lower-level runtime metrics or per-Worker hard budgets for cost control. ## Uncertainties - Notion calls $0.0023 a typical run cost rather than a fixed universal tariff; heavier executions can consume more credits. - Workers remain labeled beta, so pricing mechanics and administrative controls can still change. - Some Notion help pages indexed at different times show slightly different defaults for whether Workers are enabled; current workspace behavior should be verified in-product. ## Sources - [Understand pricing for Workers in Notion](https://www.notion.com/en-gb/help/understand-pricing-for-workers) — Notion · official pricing documentation. Primary source for the August 11 billing cutover, typical per-run cost, run definitions, examples and cost-control guidance. - [Workers, now in your Notion credits dashboard](https://www.notion.com/releases/2026-07-24) — Notion · official release · 2026-07-24T00:00:00+12:00. Announcement that Worker usage was visible before the billing cutover so teams could size credits. - [Run custom code with Workers in Notion](https://www.notion.com/help/run-custom-code-with-workers) — Notion · official documentation. Product scope, plan availability and operational role of Workers.