Beginning
Imagine this: A new order email arrives. Your automation logs it into a Google Sheet, like it's done since Lesson 4. But what if, at the exact same moment, your team also got a Slack notification — instantly, without anyone having to check the spreadsheet?
That's the power of a multi-step scenario. Instead of one Trigger leading to one Action, a single event can now set off a whole chain of actions, each one happening automatically. By the end of this lesson, your automation won't just log data — it'll notify your team in real time too.
In this lesson, you'll learn:
- What a multi-step scenario actually means
- How to add a new module to the end of an existing scenario
- How to connect Slack as a third app in your automation
- How to map data from an earlier module (not just the one right before it) into a new step
Core Concept: The Assembly Line
Think of your scenario as an assembly line. Each module is a station, and the item (your data) moves down the line, station by station, getting something done at each stop.
So far, your line has had two stations after the Trigger:
Gmail (Trigger) → Filter (Checkpoint) → Google Sheets (Action)
In this lesson, we're adding a third station to the end of that line:
Gmail (Trigger) → Filter (Checkpoint) → Google Sheets (Action) → Slack (Action)
The key idea: one Trigger can now set off multiple actions, all from a single event. This is exactly how real automation systems used by businesses work — one thing happens, and several useful things follow automatically.
Tool Walkthrough: Adding a Third App
Step 1 — Open Your Existing Scenario
Go back to the scenario you built in Lesson 5 (Gmail → Filter → Google Sheets). We're extending it, not starting fresh.
Step 2 — Add a New Module at the End
On the right side of your Google Sheets module, you'll see a small "+" icon. Click it — this is how you always add a new module to a scenario: at the end of the current chain, never squeezed in the middle.
Step 3 — Search for Slack and Choose an Action
In the search box, type Slack, select it, and choose the "Send a Message" action. This will be your new Action Module — the second thing that happens after your Trigger fires.
Step 4 — Connect Your Slack Workspace
The first time you use Slack in Make, you'll be asked to create a Connection. Click "Add" or "Sign in with Slack," choose your workspace, and allow the requested permissions. Like Gmail and Sheets before it, this Connection is saved for future use.
Step 5 — Map Gmail Data into Your Slack Message
In the message content field, you'll build a message using data from earlier in the scenario — not just from Google Sheets (the module right before Slack), but from Gmail, several steps back. Something like:
New order received: {Subject} from {From (name)}
Click into the message field, and you'll see fields from both the Gmail and Google Sheets modules available to insert. This is an important lesson in itself: a module can pull data from any earlier step in the scenario, not just the one directly before it.
Step 6 — Test the Full Chain
Choose a Slack channel to post to, then click Run once. Send yourself a test email matching your filter condition, and watch all three actions complete: the row gets added to your Sheet, and a message appears in your Slack channel — all from one email.
You've just built a true multi-step automation — one event, multiple real actions.
Real Example: Why This Matters for Freelancing
This is exactly the kind of upgrade that turns a basic automation into a premium one. A client who's happy with "my orders get logged in a spreadsheet" becomes thrilled with "my team gets notified on Slack the second an order comes in, and it's already logged for our records."
This single addition — one more module — can be the difference between a $50 automation gig and a $200+ one, because it solves a second problem (team awareness) on top of the first (record-keeping), using the same Trigger you already built.
Common Mistakes
Mistake 1: Adding a new module in the wrong place
Clicking the "+" between two existing modules (instead of at the very end) inserts a module into the middle of the chain, which breaks the intended order. Always extend from the rightmost end unless you specifically mean to insert a step in the middle.
Mistake 2: Creating a new Slack Connection every time
Just like Gmail and Sheets, Slack Connections should be reused. Always check if a Connection already exists before creating a new one — it keeps your account organized and avoids confusion later.
Mistake 3: Not testing after each new module
When a scenario has four or five modules, it's tempting to build several steps at once and test only at the end. If something breaks, you won't know which module caused it. Testing after every single addition keeps troubleshooting fast and simple.
Try This Yourself
Before moving to Lesson 7, try this extension:
- Add a second field to your Slack message, such as the sender's email address
- Change the Slack channel the message posts to, and re-test to confirm it updates correctly
Key Takeaways
- A multi-step scenario means one Trigger leading to two or more Actions in sequence
- New modules are always added at the end of the chain, using the "+" icon
- A module can map in data from any earlier step in the scenario, not just the one directly before it
- Testing after each new module addition makes debugging far easier than testing only at the end
- Adding real-time notifications (like Slack) on top of data logging is a simple way to deliver more value in freelance automation work
Frequently Asked Questions
Can I add more than one new app after Slack?
Yes. Scenarios can have many modules — you'd simply repeat the same process: click "+" at the new end of the chain, search for the app, and configure it.
What if I want Slack to run before Google Sheets instead of after?
You can drag and reorder modules in most cases, or rebuild the sequence by adding modules in the order you want. The important part is that the Trigger always stays first.
Does adding more modules cost more on the free plan?
Each module execution counts as one operation toward your plan's monthly limit, so a 4-module scenario uses more operations per run than a 2-module one. This is worth keeping in mind as your automations grow, especially on Make's free tier.
Next Lesson Preview
In Lesson 7, we'll focus on Testing & Debugging — now that your scenarios are getting more complex, you'll learn a systematic way to find exactly where something went wrong and fix it quickly.
Navigation:
← Previous: Lesson 5 — Filters & Conditional Logic
→ Next: Lesson 7 — Testing & Debugging Your Automations
🏠 Back to Course Hub