Scenario

In Make (formerly Integromat), a "scenario" is the name for a single automation — the complete flow of connected modules that runs from a trigger through to its final action. It's Make's equivalent of a Zapier "Zap" or an n8n "workflow." Why the term matters: on Make, pricing, execution limits, and organization are all measured per scenario. Each scenario has its own trigger (webhook, scheduled, or polling), its own canvas of modules, and its own run history you can inspect when something breaks. A scenario can contain routers, iterators, aggregators, filters, and error handlers, so a single scenario often orchestrates work across many apps at once. Practical note: keep scenarios focused — one job per scenario — rather than building one giant scenario that does everything. Smaller scenarios are easier to debug from run history, cheaper to re-run after a failure, and safer to edit without breaking unrelated automations. You can also chain scenarios by having one trigger another via webhook.