Operation (Make)

An operation is Make's billable unit of work: one run of a module that processes a single bundle of data. Each time a module reads, checks, or acts on a piece of data inside a scenario, it consumes one operation, and your plan includes a fixed number per month.

How operations are counted

A bundle is one unit of data — an email, a contact, a row, an API response. A module charges one operation per bundle it handles. That means:

• The trigger module counts as an operation each time it runs.
• A filter step counts as an operation even if it stops the flow.
• An iterator looping over ten line items charges ten operations for that step alone.

So a four-module scenario that fires on each of 500 form submissions consumes roughly 4 × 500 = 2,000 operations that month. Error-handler directives like Rollback, Break, and Resume are notable exceptions that do not consume operations.

Operations vs credits

In August 2025 Make began migrating its metering from "operations" to "credits." For standard module runs the math is the same — one module execution costs one credit, just as it previously cost one operation. The counting model (one charge per module run per bundle) carries over regardless of the label.

Why operations matter

Operations are how Make's pricing scales with volume, similar to how Zapier bills by task. The more modules a scenario has and the more often it runs, the faster you burn through your monthly allowance. Complex, high-volume automations can consume operations far faster than a step count suggests, because loops and per-bundle processing multiply the total.

For a fixed job like Stripe-to-Slack payment alerts, a flat-priced tool such as ChargeBell avoids per-operation metering entirely — your best sales month never becomes your biggest automation bill.