How to filter data in Make.com — routes and filters
Updated 2026-08-01
Many Make.com threads ask how to filter data. Bundles vanish, the wrong branch runs, or nothing reaches Google Sheets. Filters and routers are powerful — and a common reason a scenario "stopped working" when the data shape changed.
Filters vs routes
A filter on a module connection decides whether the next module runs for that bundle. A router splits the flow into branches with their own conditions.
If every bundle fails a filter, later modules look dead even though the trigger still fires. Check the execution inspector: filtered-out bundles are not the same as a module error.
When filtering creates fake outages
A renamed field, empty optional value, or stricter condition after a provider API change can drop all items. The scenario is on; the data never passes the gate.
If you also see BundleValidationError after a filter, fix the surviving bundles' mappings — do not only loosen filters.
Paste the error for a sourced diagnosis
If you still have the execution log, use the free tool — Make's docs only, every claim linked, or an honest refusal when coverage is missing.
Example you can try: My Make scenario runs but the Google Sheets module never receives data. I think a filter is blocking bundles.
Official Make documentation
FAQ
Why does the scenario run but Sheets stay empty?
Often every bundle was filtered out, or a router branch never matched. Open a recent execution and see whether the Sheets module was reached.
Can Eviverse design my filters for me?
Not today. The free tool diagnoses errors from logs. Filter design stays in Make's scenario builder; use Help Center for router patterns.
Related guides
- BundleValidationError on Google Sheets in Make.com
- Why your Make.com scenario suddenly stopped working
- Make.com webhook not receiving data
Eviverse is independent and not affiliated with Make. These guides are original explanations with links to Make's public Help Center — not republished documentation.