Module (Make)

A module is one step in a Make scenario. It takes data in, does one thing with it in an app, and passes the result to the next step. You connect modules on the canvas to build a workflow. A module is roughly the same as a Zapier action.

Types of modules

• Triggers start a scenario when new data appears. Instant triggers run on a webhook. Polling triggers check on a schedule.
• Actions create, update, or delete data, such as sending a message or adding a row.
• Searches look up existing records and return matches.
• Flow-control modules, such as routers, iterators, and aggregators, control how bundles move through the scenario.

Each app has its own modules, so Stripe offers a different set than Google Sheets.

Modules and operations

Each time a module processes a bundle of data, it uses one operation, Make's billing unit. A scenario's cost depends on how many modules it has and how often they run. If a loop sends ten items through one module, that module uses ten operations.

Modules and ChargeBell

Building a Stripe to Slack scenario in Make means choosing modules, mapping fields between them, and fixing the mapping when an app's API changes. ChargeBell handles the Stripe connection and the Slack message format, so there are no modules to set up or operations to count.