Module (Make)

A module is a single step in a Make scenario: one app-specific action that receives data, does something with it, and passes the result to the next step. Modules are the building blocks you drag onto the canvas and connect to form a workflow, and each is the rough equivalent of a Zapier action.

Types of modules

Make groups modules by the role they play in a scenario:

• Triggers start a scenario by watching for new data — an "instant" module fires on a webhook, while a "polling" module checks on a schedule.
• Actions create, update, or delete data in an app — sending a message, adding a row, calling an endpoint.
• Searches look up existing records and return matches.
• Flow-control modules like routers, iterators, and aggregators shape how bundles move rather than talking to an app.

Each app in Make exposes its own set of modules, so a Stripe connection offers different modules than a Google Sheets one.

Modules and operations

Every time a module runs and processes a bundle of data, it consumes one operation — Make's billable unit. A scenario's cost is therefore driven by how many modules it contains and how often each one runs. A loop that passes ten items through a module charges ten operations for that single step.

Why modules matter

Because modules are per-app, wiring a scenario means learning each connector's modules, mapping fields between them, and maintaining that mapping as APIs change. This flexibility is the strength of a general automation platform and also its overhead.

For a fixed task like Stripe-to-Slack alerts, ChargeBell handles the connection and message formatting for you, so there are no modules to configure, no field mapping to maintain, and no per-operation meter to watch.