Filtering in Make.com: Step-by-Step Guide

Filtering in make.com lets you decide exactly which data continues through your scenario and which data is stopped or redirected. By adding filters, you can build precise, conditional automations that only run when specific criteria are met.

This guide explains how filtering works in make.com, which operators you can use, how to set up conditions between modules, and how to test and troubleshoot your filters.

What filtering does in Make.com scenarios

In every scenario, data moves from one module to the next in bundles. Filters in make.com act as checkpoints between these modules. When data reaches a filter, the system evaluates your condition and decides whether that bundle can pass.

If the condition is met, the bundle continues to the next module. If the condition fails, the bundle is discarded or follows another route, depending on how you designed the scenario.

How filters work in Make.com

A filter in make.com is always placed between two modules on a route. Each filter contains one or more conditions that must be satisfied for the bundle to pass.

Every condition is made of three basic parts:

• Left operand – usually a mapped value from the previous module output, but it can also be a manual value or function.
• Operator – the comparison type, such as equals, greater than, contains, or matches a pattern.
• Right operand – a static value, mapped value, or expression to compare against.

When a bundle reaches the filter, make.com evaluates the condition using these three parts. If you have multiple conditions, the filter also needs a logical rule to define how they combine.

Where filters appear in a Make.com scenario

In the scenario editor, filters in make.com appear as small funnel icons between modules. You can click a route between two modules to add, edit, or remove a filter at any time, even while you are still designing the workflow.

Filters only affect the route they sit on. If your scenario splits into multiple routes using a router, each route can have its own independent filters and rules.

Available filter operators in Make.com

Operators control how make.com compares the left and right operands. They let you test equality, presence, numbers, dates, and text patterns.

Common comparison operators in Make.com

• equals / does not equal – checks whether two values are identical or different.
• less than / less than or equal to – compares numeric or date values to see if one is smaller.
• greater than / greater than or equal to – compares numeric or date values to see if one is larger.
• is empty / is not empty – checks whether a value exists or is missing.

Text and list operators in Make.com filters

• contains / does not contain – verifies whether a string or collection includes a specific value.
• starts with / ends with – tests the beginning or end of a string.
• matches pattern – uses pattern or regular expression style matching, depending on the module output and your configuration.

Use numeric operators for amounts, IDs, and dates, and use text operators when you need to check names, subject lines, or free-form text content.

Creating a filter in Make.com

Follow these steps to add a new filter in make.com between two modules in an existing scenario.

1. Open the scenario

   In your dashboard, open the scenario where you want to control the data flow.

2. Identify the route

   Locate the connection line between the modules where data should be filtered.

3. Add a filter

   Click the route. In the context menu, choose the option to add or edit a filter.

4. Name the filter

   Give the filter a clear, descriptive name so you recognize it when reviewing scenario runs.

5. Define the condition

   Select the left operand, choose the operator, and then set the right operand. You can map output fields from previous modules or type a fixed value.

6. Save the filter

   Confirm the settings and save. The funnel icon will now appear on the route between the two modules.

Once created, the filter becomes part of your scenario logic. During execution, only bundles that meet the filter rule will continue past that point.

Combining conditions in Make.com filters

Often, you need more than one condition. Make.com allows you to create complex logical expressions using multiple conditions in a single filter.

Using AND logic in Make.com

When you combine conditions with AND, every condition must be true for the bundle to pass the filter. This is useful when you want very specific matches, such as a status and a minimum amount both being met.

Example logic with AND:

• Status equals Paid
• AND Amount greater than 100

Only bundles that are paid and higher than 100 will pass.

Using OR logic in Make.com

When you combine conditions with OR, only one of the conditions has to be true. Use this when data should continue if it matches any one of several options.

Example logic with OR:

• Country equals US
• OR Country equals CA

Either value allows the bundle to pass the filter.

Nested filter logic in Make.com

For more advanced rules, make.com lets you group conditions to create nested expressions. You can mix AND and OR so that some conditions must all be true, while others only need one match.

For example, you can require that a contact is subscribed AND (in one of several regions OR requested a specific product). Grouping the conditions correctly is essential, so take time to double-check the logical structure.

Routing data with filters and routers in Make.com

Filters in make.com become especially powerful when used together with routers. A router lets you branch a scenario into multiple routes. By placing different filters on each route, you can send different bundles to separate processing paths.

For instance, you might have one route for high-priority items, another for standard items, and a third that stops all other data. Each route would use its own filter condition to select which bundles are allowed through.

Testing and troubleshooting filters in Make.com

Whenever you add or change a filter in make.com, test the scenario carefully to confirm that data is flowing as expected.

Using scenario execution history

Run the scenario and then open the execution details. You can inspect each module, including the filters, to see which bundles passed and which were discarded. The visual flow makes it easier to verify that your conditions are correct.

Common issues with Make.com filters

• Incorrect data types – comparing text to numbers or mismatched date formats can cause filters to fail unexpectedly.
• Spelling and case – string comparisons in make.com are often case-sensitive, so check that values match exactly.
• Empty values – if the left operand is empty, some operators will never match. Consider using is empty or is not empty operators when needed.
• Logical grouping – misusing AND and OR or missing parentheses in grouped logic often leads to bundles being filtered incorrectly.

By reviewing execution logs and adjusting your conditions, you can refine the filter until it behaves correctly in every case.

Learning more about Make.com filtering

The official documentation provides detailed operator descriptions, screenshots, and additional examples of routing with filters in make.com scenarios. You can explore it here: Filtering documentation for Make.com.

If you need broader automation strategy help beyond the technical setup in make.com, consult the experts at Consultevo for scenario design, optimization, and integration planning.

With a solid understanding of filters, conditions, and routes, you can build highly targeted automations in make.com that respond precisely to your business rules, reduce noise, and keep every workflow clean and predictable.

Need Help With Make.com?

If you want expert help building, automating, or scaling your Make scenarios, work with ConsultEvo — certified workflow and automation specialists.

Get Help