Resources · Make integration

Scenarios Make integrationAutomate Scenarios with Make.

Tired of one giant scenario that nobody dares to touch? The Scenarios Make integration gives you 2 built-in modules to start or call one scenario from another. This guide is for builders who want smaller, reusable pieces, and it walks you through a first setup.

Try the Scenarios integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Scenarios Make integration do for you?

You get a way to chain your automations. In Make, a scenario is the automation you build, a chain of modules (each module is one brick: a trigger, an action, a search). Scenarios is a built-in app of Make, not an outside service: it lets one scenario start or call another, pass it inputs, get its outputs back and name each run.

One shared routine, called from everywhere. Say three of your automations all end by formatting a customer record the same way. Build that routine once as its own scenario, then call it from each parent scenario (most likely through the Actions module, since the doc does not map its entries). Fix it in one place and every caller benefits.

A clean entry point for helper scenarios. The doc gives one rule here: a called scenario should open with the Start scenario module. The app files its modules under two entries, Triggers and Actions, and the name of the first points to that starting side, though the doc does not spell out what sits under each.

Answers that come back. A called scenario can return outputs, so the parent can keep working with the result instead of guessing what happened.

What to keep in mind: when you change the inputs or outputs of a subscenario, the parent does not pick up the change by itself. You reopen the Call a scenario module in the parent and refresh the inputs. The good news is on the bill side: the doc states that Scenarios modules do not consume credits. Check Make pricing to see how credits work on the rest of your modules, and Make troubleshooting if a call fails. Weighing another tool for the same job? Read n8n vs Make.

Connect

How do you set up Scenarios in Make?

  1. 01

    Add a Scenarios module

    Open your scenario, click the + and type Scenarios in the search. The doc lists no prerequisite for this built-in app, so you can pick a module right away.

  2. 02

    Create a connection if Make asks

    A connection is your account of an app linked to Make once, then reused. If Make shows Create a connection here, click it and give it a name you will recognize later.

  3. 03

    Save and fill the module

    Click Save when a connection window is open, then fill the module. In a parent scenario, you pick which scenario to call; in the called one, you set the inputs it expects.

First scenario

Your first scenario with Scenarios

GoalWhen a new order lands in your store app, Make calls a separate scenario that handles it and hands the result back.

  1. 01

    Create the parent scenario

    From the Scenarios page of Make, create a new scenario and click the + to add the first module, for example the new order trigger of your store app.

  2. 02

    Link your store account

    Pick that trigger, click Create a connection and authorize Make. Once linked, Make can list what it reads from your store.

  3. 03

    Add the Actions module

    Click the + on the right of the trigger, search Scenarios and add Actions, the entry that most likely holds the call (the doc does not say). Choose the scenario to call and map the order data from the previous module into its inputs.

  4. 04

    Test with Run once

    Click Run once and place a test order. Each module shows the bundles it received (a bundle is one item passing from module to module, here one order).

  5. 05

    Schedule it and switch it on

    Set the schedule on the first module (a new scenario checks every 15 minutes by default), then turn the scenario on. On the Free plan, 2 active scenarios is the cap.

Modules

The 2 modules of the Scenarios app

Scenarios gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

All Scenarios modules are free to use, as they do not consume credits.

You should use the Start scenario module in a called scenario.

Updates to scenario inputs and outputs in subscenarios are not automatically reflected in parent scenarios. To sync changes, return to the parent scenario, open the Call a scenario module, and update the scenario inputs. Scenario outputs should be updated in the subsequent modules of the parent scenario

Scenarios1

Triggers

ActionIn the docs only

First of the two entries of the app, its name suggests the start of a run. What the doc states for sure: a called scenario should begin with the Start scenario module, so it can receive inputs from its parent.

When to use it
you are building a subscenario, say the routine that tags a new lead, and want other scenarios to reach it.
Watch out
despite its name, Make types it as an action, not a scheduled or instant trigger. It watches no app by itself.
Scenarios2

Actions

ActionIn the docs only

This second entry groups the other moves of the app. Across both entries, the doc lists what Scenarios can do: call a scenario, return its outputs to the parent and give each run a custom name, all without spending credits.

When to use it
the same steps repeat in several automations and you would rather maintain them once.
Watch out
after you change a subscenario, open the Call a scenario module in the parent and refresh its inputs by hand.
Need help

Need help automating Scenarios with Make?

A person reads every message.

FAQ

Scenarios Make integration: common questions

01Is the Scenarios Make integration free?
Yes. Scenarios is a standard built-in app, available from the Free plan, and the doc states its modules do not consume credits at all. The limits you will feel come from your Make plan: the Free plan allows 2 active scenarios, a 15 minute minimum between scheduled runs, 5 minutes per execution and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lift the interval to 1 minute and allow unlimited active scenarios, which matters once you split work into several parent and child scenarios.
02What do you need to connect Scenarios to Make?
Just a Make account. The doc gives no prerequisite for this built-in app, since it works on scenarios that already live in your Make account. If the editor asks for a connection when you add a module, follow the usual steps: click Create a connection, name it if you like, authorize, then click Save. Plan ahead on the Free plan: a called scenario is a scenario too, so it most likely takes one of your 2 active slots.
03Can a Scenarios module start a run in real time?
Not on its own, because the app has no scheduled or instant trigger that watches an outside app. The parent scenario decides when things happen. Start it with a trigger from another app, which fires instantly through a webhook if that app offers one, or with a schedule on the first module, every 15 minutes by default. The called scenario then runs from the call in the parent, and the doc recommends it opens with the Start scenario module.
04What if a Scenarios module is missing or a limit gets in the way?
The app has no Make an API Call module, so there is no generic fallback inside it. The limit people hit most often is the sync between parent and child: new inputs or outputs in a subscenario do not appear in the parent until you open the Call a scenario module and update them. If what you need goes beyond starting, calling and returning outputs, look at the modules of the app you work with, or ask the team behind this page to review your setup.
05Should you use Make or n8n for Scenarios?
It depends on where the rest of your automations live. Scenarios is a Make built-in: it only calls scenarios inside Make, and its modules cost no credits, which makes it a natural choice if your team already builds in Make. This page covers the Make side only and does not say whether n8n has an equivalent. Pick the tool your processes run on today, and use the comparison page linked above to weigh both on your own criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations