Scenario (Make)

A scenario is an automated workflow in Make. It is a chain of modules that starts from a trigger and moves data between apps. It is Make's version of a Zapier Zap.

How a scenario works

You build a scenario on a canvas by connecting modules. The first module is usually a trigger that watches for new data, such as a new payment, a new row, or an incoming webhook. The next modules act on that data. They create records, call APIs, route data, or format it. Data passes between modules in bundles, and the connections set the order.

Routers add branches. Iterators and aggregators handle loops. Filters let data through only when it meets a condition. This lets a scenario do more than a single trigger and action.

Running and scheduling

A scenario runs on a schedule, such as every 15 minutes, or right away when a webhook arrives. Each run executes the modules in order. Each time a module processes a bundle, it uses one operation, which is the unit Make bills by.

When to use one

Scenarios fit custom, multi-step work, such as syncing data across several tools or enriching records. You build and maintain the setup yourself, and cost grows with the operations you use.

For posting Stripe payment events to Slack as readable alerts, ChargeBell does the job without a scenario. It has read-only Stripe access, writes alerts in plain English, and charges a flat fee instead of per operation.