How to use filters and routers on Make

beginner 8 min read Updated 2026-03-13

Quick Answer

Routers in Make.com split workflows into multiple paths, while filters on each path control data flow based on conditions. Set up by adding a router module, configuring filters via the wrench icon, and ordering routes for evaluation. Use fallback routes for unmatched data to ensure complete processing.

Prerequisites

Make.com account
Basic scenario setup knowledge
Familiarity with trigger modules
Understanding of data bundles

Step-by-Step Instructions

Access Scenarios Dashboard

Log in to your Make.com account and navigate to the Scenarios section in the left sidebar. Click Create a new scenario or select an existing one to edit.[1][3][5]

Set Up Trigger Module

Add a trigger module like Webhook or Google Forms as the starting point. Click the + icon after the trigger, search for your app, configure connection details, and run Run once to generate sample data bundles.[2][6][7]

Always test with <code>Run once</code> to ensure data flows correctly.

Add Router Module

Click the + icon on the trigger's output or right-click the connection and select Add a Router from Flow Control. The router appears with one default output; click the central + to add more routes, up to 40 branches.[1][2][4][5]

Configure Filters on Paths

Hover over a router output connection, click the wrench icon, and select Set up a filter. Enter a Label, add conditions like {{1.service_type}} Equal to membership, choose AND/OR logic, and click OK. Repeat for each route; no filter means all data passes.[1][2][4][6][8]

Use mapped data from prior modules like <code>{{1.status}}</code> for dynamic conditions.

Set Up Fallback Route

Add an extra route with the router's + button. Click the wrench, select Set up a filter, check Yes for Fallback route? (shown by special arrow icon), add a label like Default, and save. It processes items failing other filters.[1][3][5]

Fallback ensures no data is lost if conditions don't match.

Attach Modules to Routes

Click + on each route's output to add actions like Google Sheets or email. Map data with bundle picker, e.g., {{1.company}}. Right-click modules to Rename descriptively, such as Send Membership Email.[1][2][3][7]

Order Routes for Evaluation

Drag routes left/right on the canvas to set top-to-bottom evaluation order. Items test against every filter independently; matching multiple sends data to all routes.[1][5]

Routers evaluate all paths separately, allowing multi-route processing.

Test the Scenario

Click Run once in the editor. View Execution history at bottom: green paths process, gray/orange show filtered/stopped. Use Re-execute or resubmit data to test branches.[1][2][3][6]

Test varied inputs to verify each filter and route.

Common Issues & Troubleshooting

No items passing a route

Check filter conditions match incoming data types and values exactly; verify mappings like <code>{{1.field}}</code>.[1]

Items going to unexpected routes

Review overlapping filters or unfiltered default routes; adjust conditions to avoid matches on multiple paths.[1]

Scenario stops at the router

Ensure at least one route has satisfiable conditions or add a fallback/unfiltered catch-all branch.[1]

Filter not recognizing data

Confirm data from previous modules is available; use <code>Run once</code> to inspect bundles and adjust operators like <strong>Contains</strong> or <strong>Equal to</strong>.[2][6]

Multiple conditions not working

Set AND/OR logic correctly in filter setup; test each condition separately before combining.[2]

Visit Make View Make Pricing