Make.com Scenarios

Scenarios are Make.com's equivalent of workflows — the visual automations you build on the canvas. Understanding how scenarios work — their structure, their execution model, and their key features — is essential for building effective Make.com automations. This guide covers scenarios comprehensively, from basic structure to advanced execution patterns.

MJK Supplies · Feb 4, 2026 · 4 min read

ShareX in f ↗

What a Scenario Is

A Make.com scenario is a visual automation that runs when triggered and executes a series of connected modules. Each scenario has:

One trigger module: The starting point that defines when the scenario runs (a schedule, a webhook, or an event in a connected app)
One or more action modules: The steps that execute after the trigger — fetching data, transforming it, sending it to other services
Connections between modules: The lines that show how data flows from one module to the next
Optional: Routes and filters: Conditional branches that allow different paths based on data values

When a scenario runs, it executes each module in sequence from the trigger. The output of each module is available as input to subsequent modules.

Trigger Types

Schedule trigger: Runs the scenario at a defined interval — every X minutes, every hour, at a specific time each day. Make.com "polls" the trigger service for new data on each run.

Webhook trigger: A unique URL that external services POST data to. When a POST arrives, the scenario runs immediately with the received data. Webhooks enable real-time automation.

Watch triggers: App-specific triggers that check for new events — "Watch new emails" (Gmail), "Watch new contacts" (HubSpot), "Watch new orders" (Shopify). Schedule-based behind the scenes.

Instant triggers: App-specific triggers that use webhooks internally — they fire immediately when an event occurs without waiting for a scheduled check. Not all apps support instant triggers.

The choice of trigger affects both latency (schedule = up to X minutes delay; webhook = immediate) and cost (schedule-based triggers run even when nothing happened; webhook triggers only run when there's data).

Data Flow and Mapping

Data flows through a scenario as "bundles." Each module receives bundles from the previous module, processes them, and outputs bundles to the next module.

Mapping data: When configuring a module, click in any field to see the data available from previous modules. Select the field to insert it. You can combine static text with dynamic values: "Hello, {{1.firstName}}!" — where 1 is the first module's number.

Functions: Make.com includes built-in functions for data manipulation:

formatDate(date, "YYYY-MM-DD") — format dates
lower(string) — convert to lowercase
parseNumber(string) — convert string to number
first(array) — get the first element of an array
if(condition, valueIfTrue, valueIfFalse) — conditional values

Use functions in field mappings to transform data without needing a separate module.

Routes and Filters

Router module: Splits the scenario into multiple branches. Each branch can have a filter that determines which data flows through it. Use routers when different data needs different processing — high-priority tickets go to one path; low-priority tickets go to another.

Filters: Added to connections between modules. Conditions that must be true for data to pass through. Filter examples: "Only continue if {{1.email}} contains '@'", "Only continue if {{1.amount}} is greater than 100".

Multiple routes: A router can have 2+ routes. Use this for classification scenarios where data is sorted into different downstream paths based on content.

Error Handling

Make.com's error handling is one of its strongest features. Every module has an "error handler" connection — a path that only activates when that module fails.

Adding an error handler: Right-click a module and add an error handler route. This creates a separate path that receives error data. Common error handling actions: log the error to Airtable, send a Slack alert, retry the failed operation.

Error handling types:

Resume: Continue from the next module even though this one failed
Rollback: Undo all changes made in this execution (for atomic operations)
Commit: Finalize all changes made so far and stop
Break: Stop the execution and log it as incomplete
Ignore: Silently continue without processing this bundle

Retry: Configure an error handler to retry the failed module a certain number of times before giving up. Essential for rate-limited APIs.

Scenario Scheduling

Make.com scenarios run on a schedule defined in the "Scheduling" panel. Options:

As soon as possible: Maximally frequent (every minute on paid plans)
At regular intervals: Every N minutes, hours, days
At a specific time: Once per day at a defined time
Custom: Cron-style scheduling for complex patterns

More frequent scheduling uses more operations (each module execution = 1 operation, every run). Balance freshness (how quickly new data is processed) against cost (operations per month).

For webhooks and instant triggers, scheduling is not relevant — the scenario runs when data arrives.