Make.com 101
Make.com is visual automation. You connect triggers to actions, and data flows between services automatically. It's the glue that holds your stack together.
Scenario Builder
A Make.com scenario is a chain of modules. Each module does one thing: watch for an event, transform data, or send it somewhere. Explore three real scenarios below.
When someone subscribes, send a welcome email, store in database, notify your Slack.
This is a simulation — click to see what each module would process. In production, real data flows through Make.com automatically.
How Modules Connect
Every module receives data from the previous module and passes data to the next. You map fields between them — that's the core of Make.com.
Understanding {{1.email}} syntax: The number refers to the module's position in the scenario. {{1.email}} means "grab the email field from module #1 (the Webhook)." {{now}} is a built-in function that returns the current timestamp. You'll use this pattern constantly — it's how data flows between modules.
Here's how data flows through the Email Capture scenario above:
{ "email": "user@example.com", "name": "Alex" }
// Module 2 — Resend uses {{1.email}} to pull the email from Module 1:
To: {{1.email}} → becomes: user@example.com
Subject: "Welcome, {{1.name}}!" → becomes: "Welcome, Alex!"
// Module 3 — Supabase also pulls from Module 1 to save the subscriber:
email: {{1.email}}
name: {{1.name}}
joined_at: {{now}} → becomes: current timestamp
Build Your Own Scenario
Drag modules from the palette into the canvas to create your own automation.
Tip: Start with a trigger (Webhook or Schedule), then add processing steps, and end with an output (Slack, Supabase, or Email). A good first scenario: Webhook → Supabase → Slack — receive data, store it, notify yourself.
Drop modules here to build your scenario...
Error handling: Add a Router module to create parallel paths — one for success, one for failure. Never let a scenario fail silently.
Rate limits: Most APIs have rate limits. Use Make.com's built-in delay/sleep to stay under them.
Testing: Always use "Run Once" to test before turning on scheduling. Check every module's output.
Scenario Module Matcher
Tap one on the left, then its match on the right