Beginning
Imagine this: Your Gmail-to-Sheets automation from Lesson 4 is running perfectly — every single email that lands in your inbox gets logged as a new row. But after a day, your sheet is full of newsletters, promotions, and random notifications mixed in with the actual client inquiries you care about.
This is the exact moment every automation builder hits: your system works, but it's not smart yet. It does everything, when what you actually want is for it to do the right thing.
That's what Filters solve. By the end of this lesson, your automation will only act when conditions you choose are actually met — turning a simple "log everything" system into an intelligent one.
In this lesson, you'll learn:
- What a Filter is and how it controls your automation
- How to set conditions (equals, contains, greater than, and more)
- How to combine multiple conditions using AND / OR logic
Core Concept: The Checkpoint
Think of a Filter as a security checkpoint sitting between your Trigger and your Action. Every time your Trigger fires, the data has to pass through this checkpoint first. If it meets the condition you set, it's allowed through to the next Module. If it doesn't, the automation simply stops there for that item — nothing happens, no error, no row added.
This is the foundation of "if this, then that" thinking: if the condition is true, then continue; if not, stop. A Filter always sits on the connection line between two Modules — never inside a Module itself.
Tool Walkthrough: Adding a Filter to Your Automation
Step 1 — Open Your Existing Scenario
Go back to the Gmail-to-Sheets Scenario you built in Lesson 4. We're going to upgrade it, not start over.
Step 2 — Click the Connecting Line
Between your Gmail module and your Google Sheets module, there's a small dotted line with a wrench icon. Tap directly on that line (or the small icon near it) — this opens the option to add a Filter right at that exact point in the flow.
Step 3 — Set Your Condition
A panel opens where you define the rule. For this example, set:
Field: Subject (from the Gmail module)
Condition: Text contains
Value: New Order
This means: only emails whose subject line contains the words "New Order" will be allowed to continue to Google Sheets.
Step 4 — Name Your Filter (Optional but Recommended)
Give the filter a clear label like "Only New Orders." This isn't required, but it makes your Scenario far easier to understand later — both for you and for any client who looks at it.
Step 5 — Test with a Matching Email
Send yourself a test email with "New Order" somewhere in the subject line, then click Run once. You should see the automation pass through cleanly and a new row appear in your Sheet.
Step 6 — Test with a Non-Matching Email
Now send a test email with an unrelated subject line, like "Weekly Newsletter," and run the Scenario again. This time, the Gmail module still fires, but the Filter blocks the data — no new row gets added to your Sheet.
This before-and-after comparison is exactly how you confirm a Filter is actually working, not just sitting there doing nothing.
Real Example: Where This Matters
Imagine a freelancer managing automation for an online store. The client's inbox receives dozens of emails a day — order confirmations, newsletters, spam, support tickets. Without a Filter, every single one would get logged into the order-tracking spreadsheet, making it useless.
With a Filter like "Subject contains 'New Order'," only genuine order emails get logged — automatically separating signal from noise. This single Filter is often the difference between an automation a client actually trusts and one they immediately distrust after seeing junk data in their sheet.
Common Mistakes
Mistake 1: Making the condition too strict
If your filter looks for the exact text "New Order" but the real email subject is "NEW ORDER!!" or "New order #1234," a strict match might fail depending on the condition type you chose. Understanding "contains" versus "exact match" saves a lot of confusion here.
Mistake 2: Not testing both outcomes
Many beginners test only with a matching email and assume the Filter works. Without also testing a non-matching email, you can't actually confirm the Filter is blocking anything — it might be letting everything through without you realizing it.
Mistake 3: Confusing AND and OR
With AND, every condition you add must be true for the data to pass. With OR, only one condition needs to be true. Using AND when you meant OR (or vice versa) is one of the most common beginner mistakes, and it silently breaks automations in ways that are hard to notice at first.
Try This Yourself
Before moving to Lesson 6, extend what you just built:
- Add a second condition to your Filter: "From (email) contains" a specific sender's address
- Set the logic to AND, so only emails that match both the subject and the sender get through
- Test it with an email that matches only one of the two conditions, and confirm it correctly gets blocked
Key Takeaways
- A Filter acts as a checkpoint between two Modules, letting through only data that meets your condition
- Filters never go inside a Module — they live on the connecting line between two Modules
- AND requires every condition to be true; OR requires only one
- Always test both a matching and a non-matching case to confirm a Filter is actually working
- Clear, well-named Filters make automations easier to understand and maintain later
Frequently Asked Questions
What happens to emails that get filtered out — are they lost?
No. The email still exists in your Gmail inbox as normal. The Filter only stops that specific automation from acting on it; nothing about the original email is deleted or changed.
Can I add more than one Filter in the same Scenario?
Yes. You can place Filters at multiple points in a longer Scenario, each controlling a different step based on different conditions.
Is a Filter the same as an "if/else" branch?
Not quite. A Filter only has one path — true continues, false stops. For true branching (different actions depending on the condition), Make uses a separate feature called Router, which we'll cover in a later lesson.
Next Lesson Preview
In Lesson 6, we'll go beyond two apps and build a Multi-Step Scenario — adding a third app (like Slack) to your automation, so a filtered, relevant email doesn't just get logged in a Sheet, but also triggers an instant team notification.
Navigation:
← Previous: Lesson 4 — Your First Automation: Connect Gmail to Google Sheets
→ Next: Lesson 6 — Multi-Step Scenarios: Connecting 3+ Apps Together
🏠 Back to Course Hub