Scenario (Make)

A scenario is Make's name for an automated workflow: a visual chain of modules that starts from a trigger and runs in sequence to move and transform data between apps. It is Make's equivalent 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 — a new payment, a new row, an inbound webhook. Subsequent modules act on that data: creating records, calling APIs, routing, or formatting. Data flows between modules as bundles, and the connections between them define the order of execution.

Scenarios can branch with routers, loop with iterators and aggregators, and include filters that let data pass only when conditions are met. This makes them well suited to multi-app logic that goes beyond a simple trigger-to-action pair.

Running and scheduling

A scenario runs either on a schedule (for example, every 15 minutes) or instantly when triggered by a webhook. Each run executes the modules in order, and every module run that processes a bundle consumes one operation — the unit Make uses to meter and bill usage.

When to use one

Scenarios shine for custom, multi-step integrations: syncing data across several tools, enriching records, or orchestrating logic that no off-the-shelf product covers. The trade-off is that you build and maintain the wiring yourself, and cost scales with how many operations the scenario consumes.

For a narrow, common job like turning Stripe payment events into readable Slack alerts, a dedicated product such as ChargeBell replaces a hand-built scenario — read-only, plain-English, and priced as one flat fee rather than metered per operation.