AIAP Topic Courses·Make·07:13

Scenarios and Modules: Recipes, Employees, and the Relay Baton

Samruti Make trainer - builds a Google Forms to Google Sheets scenario live on a free Make plan

The short version

A scenario is a complete workflow - a recipe - with one trigger, multiple possible actions, a visual flowchart, and automatic runs; folders organise them; think of each as an employee with a job description (0:00-0:03).
A module does exactly one thing: triggers start the scenario (watch Gmail, form submitted, new row), actions do something (send email, create contact, post), searches look things up (a customer in a database, a file in Drive). Data passes module to module like a relay baton (0:03-0:06).

At a glance, three clicks deep

Skim here first: the closed row is the glance, open is the study card with the key points and timestamps, and the ↓ link drops to that concept's full write-up below.

01Scenarios, modules, and the three module typesScenario = workflow;›

Scenario = workflow; module = step; trigger / action / search.

Scenarios (0:00-0:03)

Modules (0:03-0:06)

↓ Full write-up of this concept

The concepts in full

Scenarios, modules, and the three module types

The scenario is the recipe. Each module is one step. The data is the baton passed from runner to runner.

Scenario: one trigger point, several possible actions, a visual flowchart, runs automatically; grouped in folders (marketing, sales). Module: one step - Trigger (watch new Gmail, form response, new Sheets row), Action (send email, create CRM contact, update spreadsheet, post to social), Search (find a customer, find a file). Output of one module becomes input of the next.

Why it matters

The two nouns every Make conversation uses.

This idea elsewherecontinuesBuilt live in lesson 4

Tools referenced

Tool	Coverage	Moment	Context
Make.com	demonstrated
Apify	demonstrated		Example trigger

Action items

Resources mentioned

Resources

docLesson page on the platform

Extraction notes

This page was built from an auto-generated transcript, which garbles product and people's names. Those were corrected silently in everything above and logged here for transparency. The warnings flag claims that were true on the recording day but change fast.

Transcript corrections applied

The transcript says	The trainer actually means
Charge GPT / Chart GPT / ChargeGPD	ChatGPT
cloud / Cloud AI	Claude
Mishou / Misho / MISO	Meesho
main dot com / mail dot com	Make.com

True on recording day — verify before relying

Make's free plan (2 active scenarios, 1,000 operations), the beta AI-agents tab, the 30-credit AI assistant and Google Cloud console labels all change; the scenario pattern is evergreen