Notice: This page requires JavaScript to function properly.
Please enable JavaScript in your browser settings or update your browser.
Aprenda Scenario Builder UI | Getting Started With Make.com
Workflow Automation with Make.com

bookScenario Builder UI

Note
Definition

The Scenario Builder is the main workspace in Make.com where scenarios are created, organized, tested, and scheduled. This is where most practical automation work happens.

Before building real scenarios, the focus is on orienting learners inside the Scenario Builder UI. The goal is to remove early friction and confusion, so building feels logical instead of overwhelming.

  • Core canvas controls.
  • Import and export options.
  • Right-side toolbar functions.
  • Notes, version history, and basic settings.
  • How to read inputs and outputs and visualize data flow.

The Scenario Builder is the main workspace where daily automation work happens. While the left navigation remains available, most interaction occurs on the canvas.

Scenarios should be renamed early to stay organized as more are created. Canvas display options can be toggled to show credit usage, module IDs, and route order, which helps with troubleshooting and complex logic.

The top-right area contains sharing and blueprint tools. Scenarios can be imported, exported as JSON, or copied for quick reuse. The right-side toolbar provides high-value tools such as Logs for tracking execution and Add for inserting modules, including flow control and utility tools.

Previous Versions act as a safety net, making frequent saving an important habit. Notes can be attached to modules to document logic without cluttering the canvas.

Note
Note

Most settings can be ignored at first, except data confidentiality and cycle limits. Inputs, outputs, and the flow view help visualize how data moves through the scenario. Auto Align works well for simple layouts but is less useful for complex branching.

question mark

Which statement best describes the purpose of the Scenario Builder UI in Make.com

Select the correct answer

Tudo estava claro?

Como podemos melhorá-lo?

Obrigado pelo seu feedback!

Seção 1. Capítulo 4

Pergunte à IA

expand

Pergunte à IA

ChatGPT

Pergunte o que quiser ou experimente uma das perguntas sugeridas para iniciar nosso bate-papo

Suggested prompts:

Can you explain more about how to use the blueprint import/export features?

What are some best practices for organizing scenarios and using notes?

Could you walk me through the process of visualizing data flow in a scenario?

bookScenario Builder UI

Deslize para mostrar o menu

Note
Definition

The Scenario Builder is the main workspace in Make.com where scenarios are created, organized, tested, and scheduled. This is where most practical automation work happens.

Before building real scenarios, the focus is on orienting learners inside the Scenario Builder UI. The goal is to remove early friction and confusion, so building feels logical instead of overwhelming.

  • Core canvas controls.
  • Import and export options.
  • Right-side toolbar functions.
  • Notes, version history, and basic settings.
  • How to read inputs and outputs and visualize data flow.

The Scenario Builder is the main workspace where daily automation work happens. While the left navigation remains available, most interaction occurs on the canvas.

Scenarios should be renamed early to stay organized as more are created. Canvas display options can be toggled to show credit usage, module IDs, and route order, which helps with troubleshooting and complex logic.

The top-right area contains sharing and blueprint tools. Scenarios can be imported, exported as JSON, or copied for quick reuse. The right-side toolbar provides high-value tools such as Logs for tracking execution and Add for inserting modules, including flow control and utility tools.

Previous Versions act as a safety net, making frequent saving an important habit. Notes can be attached to modules to document logic without cluttering the canvas.

Note
Note

Most settings can be ignored at first, except data confidentiality and cycle limits. Inputs, outputs, and the flow view help visualize how data moves through the scenario. Auto Align works well for simple layouts but is less useful for complex branching.

question mark

Which statement best describes the purpose of the Scenario Builder UI in Make.com

Select the correct answer

Tudo estava claro?

Como podemos melhorá-lo?

Obrigado pelo seu feedback!

Seção 1. Capítulo 4
some-alt