Workflow Billing Topology Worksheet

One business event can create one paid unit, hundreds of downstream actions, or thousands of empty scheduled checks. The difference is the workflow topology, not the label on the plan.

Interactive decision asset

Workflow Billing Topology Worksheet

Map the workflow before comparing plan limits. Values stay in this browser.

Estimate, not invoice

01 Workflow profile

Workflow name Business outcome Evidence statusConfirmed in documentation or accountEstimatedUnknown - test requiredOperational owner assigned?YesNoManual fallback available?YesNoDuplicate protectionConfirmedUnknownNone

02 Trigger and monthly volume

Trigger typeWebhook or instant eventNative polling connectorExplicit scheduleManual startUnknownPolling interval minutesActive time hours/dayActive days days/monthUseful events - normal Useful events - peak

03 Records, branches, and steps

Records/event - normal Records/event - peak Records passing the branch %Internal steps per event External actions per event Internal steps per record External actions per record

Count steps where they execute. A downstream action processing ten records may execute ten times.

04 Failure and recovery

Useful events that fail %Failed events fully rerun %Automatic step retries

Full-rerun exposure is shown as a range. Exact failed-step and retry metering remains a test item where documentation is incomplete.

05 Optional capacity check

Make credit allowance n8n execution allowance Albato transaction allowance Pabbly task allowance Policy headroom %

No buffer is prefilled. Choose it from observed volatility, continuity requirements, and the available fallback.

One-page billing brief

Shared inbox to triage record

Estimate

Checks/month2,880

Useful events20

Records processed20

Event density0.7%

Platform meter	Normal	Peak	Failure range	Capacity
Make credits	-	-	-	Not entered
n8n Cloud executions	-	-	-	Not entered
Albato transactions	-	-	-	Not entered
Pabbly tasks	-	-	-	Not entered

Main finding

Verify before buying

Every output is an assumption-led estimate. AI tokens, OCR, email or SMS, storage, databases, source APIs, and other third-party charges are excluded.

Copy briefPrint / save PDFReset example

What the worksheet calculates

The model separates business activity from platform activity. It calculates monthly checks, useful-event density, records reaching a branch, per-event steps, per-record steps, and possible full-rerun exposure.

It then translates the same assumptions separately:

• Make: trigger checks plus internal and external module activity.
• n8n Cloud: top-level production executions rather than node count.
• Albato: successful steps after the first trigger step.
• Pabbly: executed external-app actions, excluding currently listed free internal tools.

Native polling is shown as a range when empty-run behavior is not established. Automatic step retries are kept as a warning rather than converted into false precision.

How to read the scenarios

Normal uses the ordinary useful-event and record assumptions. Peak uses the realistic high-volume assumptions. Failure range starts with the peak case and adds the possible effect of full reruns. It does not pretend to know every failed-step rule.

Optional plan allowances are manual inputs because prices, quotas, and overage rules change. The worksheet never downloads live prices and never recommends a plan from quota fit alone.

What to verify in an account

Before relying on the estimate, observe the exact connector and retain:

1. The counter before and after an empty check.
2. The number and shape of records or bundles returned by a list operation.
3. The counter after a partial failure.
4. The counter after a step retry and a full rerun.
5. Whether an earlier external write was duplicated.
6. The run or execution ID and a dated screenshot or log reference.

An observed result belongs to that workflow, connector, plan, and recovery mode. Do not silently generalize it to the whole platform.

Continue the decision

Read why one workflow run becomes many billable units for the worked reasoning behind the formulas. When the usage range is credible, enter the expected monthly software cost into the Automation Cost and Payback Calculator.