Operation (Make)

An operation is Make's billing unit. It is one run of a module on one bundle of data. Each time a module reads, checks, or acts on data in a scenario, it uses one operation. Your plan includes a set number each month.

How operations are counted

A bundle is one unit of data, such as an email, a contact, a row, or an API response. A module uses one operation per bundle. So:

• The trigger module uses an operation each time it runs.
• A filter uses an operation even when it stops the flow.
• An iterator that loops over ten line items uses ten operations for that step.

A four-module scenario that runs for each of 500 form submissions uses about 2,000 operations that month. Error handlers such as Rollback, Break, and Resume don't use operations.

Operations vs credits

In August 2025, Make began renaming operations to credits. For standard module runs the count is the same. One module run on one bundle costs one credit.

Why operations matter

Like Zapier tasks, operations make your bill grow with volume. More modules and more runs use up your allowance faster, and loops can multiply the count well beyond the number of steps.

ChargeBell charges one flat price for Stripe to Slack alerts, so a busy sales month doesn't raise your bill.