What is a scenario in Make?

Make, formerly known as Integromat, is a no-code automation tool, and each automation built in it is called a scenario. A scenario is laid out on a visual canvas as a chain of modules, the building blocks that each connect to an app or do one job, such as watching for new emails, creating a record, or reformatting data. The first module is usually the trigger that starts each run.

For example, a marketing team might build a scenario that watches for new rows in a campaign spreadsheet, creates a matching task in its project management tool, passes the details to an AI model to draft a short social post, and sends the draft to a chat channel for review. Seeing the steps laid out visually makes it easier to follow how data moves from one app to the next.

Scenarios can branch into different routes, filter out items that should not continue, repeat steps for each item in a list, and handle errors in a planned way. That suits workflows with several paths, but larger scenarios can become hard to follow, so clear module names and notes help anyone who has to maintain them later.

Like any automation, a scenario depends on its app connections staying valid and on each app sending data in the expected format. Scenarios can run on a schedule or start instantly from a webhook, and each run is recorded, so checking the run history after changes is the simplest way to spot a scenario that has stopped or is producing wrong results.

An example

A Make scenario takes each new online order, adds it to an inventory spreadsheet, and sends the customer a shipping notice.