Log the run-count math behind your first Notion Workers invoice

A run-count ledger turns the first Workers invoice into a line item

Your weekly ops recap already tracks the meetings, blockers, and handoffs that keep a small team moving. The missing line is the automation behind those pages, and a sync that fires every minute generates 1,440 Worker runs in one day, compared with one run per day for a daily sync. Every scheduled sync, webhook, and agent call that does work should have a count next to the work it supports. A count is small, but it is what turns an invisible habit into a budget line.

Notion began the Workers beta on May 18, limited it to Business and Enterprise plans, including Business trials, and made it free to try during that period. Before October 15, Notion dropped the Workers beta message that the feature was free to try now; Workers credit billing begins on October 15 after the billing start had already moved from August 11. The ledger is the document that makes the cost visible before the first paid invoice.

Put the ledger in the weekly ops recap, not in a separate finance tab. The owner should be the person who already runs the recap. Each line names the Worker, the trigger, the run count, and the decision, so the total is already in the document when the credit bill arrives. Review it before blockers are discussed, because the automation is part of the operating load.

Scheduled syncs hide the biggest run counts

Scheduled sync runs are the easiest place to lose the count because they repeat without asking for permission. The trigger, not the page count, drives the bill. The every-minute case is the reason the ledger exists.

Webhooks and agent calls need the same treatment. A webhook that fires on every status change can look harmless until the tracker becomes busy. Agent tool calls are less visible because the work happens inside a conversation or a button press. Count the call, not the feeling that the agent was useful.

Separate the ledger into scheduled, event-driven, and on-demand activity. Scheduled items are the easiest to forecast because the trigger is fixed. Event-driven items require a recent count from observed usage. On-demand items get a note about who triggers them and how often that habit is growing. Keep the count repeatable, not perfect.

The credit pack is the budget test

The typical Worker price is $0.0023 per run, and a 1,000-credit monthly pack costs $10, about 4,348 runs at that rate. The run count is the real budget variable. Workspace admins can add Notion credits to Business or Enterprise plans. If the ledger shows a monthly total near the pack run total, the pack is a useful comparison. If it shows a total far above it, the team needs a decision before the next billing cycle.

Use the checklist in the weekly ops recap. It is short enough to finish in a meeting and specific enough to produce a number the owner can read.

• Name every Worker that touches the weekly cadence: scheduled sync, webhook, or agent call.
• Write the trigger for each line: daily, per event, or on demand.
• Count runs per day from the trigger, then total the month from the observed count.
• Multiply the monthly run total by the per-run cost to get the dollar line item.
• Compare that line against the monthly credit pack and mark the gap.
• Mark each line as batch, pause, or upgrade, and assign the owner.

Batching slows a sync that does not need frequent attention. Pausing removes a Worker that no longer maps to a live workflow. Upgrade is the decision to make with the number in front of the team, not after the invoice is posted. The owner writes the decision in the same line.