Make Router: catch records that match no route

Filters can leave a record with nowhere to go. A Make Router fallback route (opens in a new tab) handles records that do not pass any of the other routes.

A Router can run every ordinary route whose filter matches. Route order does not make those routes exclusive.

If each record should take just one path, Make's If-else module (opens in a new tab) runs the first condition that is true, or Else when none are true. Put more specific conditions before broader ones.

This Make Free practice routes a fictional status into a result variable. It does not send messages or update another app. Keep the scenario Inactive.

1. Build the two branches

1. In Scenarios, click Create scenario. Replace the scenario name at the top left with Router fallback practice.
2. Add Tools > Set variable. Set Variable name to status and Variable value to pending. Save the module.
3. Add Flow Control > Router after Tools.
4. On the first branch, add Tools > Set variable. Name the variable route_result and give it the value ready.
5. On the second branch, add another Tools > Set variable. Use the same variable name and the value needs_review.

2. Filter the approved branch

1. Click the connection on the first branch to open Set up a filter.
2. Set Label to Approved. Leave fallback set to No.
3. In the first condition field, select status from the first Tools module.
4. Keep Text operators: Equal to. Enter approved in the comparison field. Click Save.

Enlarge image

Full Make editor showing the Approved route condition status equal to approved

×

Open full-size image

3. Set the fallback branch

1. Click the second branch's connection.
2. Enter Needs review as its label.
3. Under Set the route as a fallback, select Yes. Leave the condition fields empty.
4. Save the filter, then save the scenario. The connection should show fallback.

Enlarge image

Full Make editor with Yes selected for the Needs review fallback route

×

Open full-size image

4. Test both outcomes

1. Click Run once with status still set to pending.
2. Check that the Approved branch passes no records and the fallback's Tools module runs. Open its result bubble and check route_result: needs_review.
3. Change the first module's value to approved, save and run again. This time, the first branch should output ready and the fallback should not run.
4. Restore pending and save if you want to repeat the first example.

Enlarge image

Full Make editor showing pending blocked by Approved and processed by Needs review fallback

×

Open full-size image

If the wrong branch runs

Inspect the first Tools module's output. Compare its actual status with the filter text, including spelling and extra spaces. Check that the token comes from the first module, and that the second branch visibly says fallback.

Make processes routes sequentially. Its Router documentation (opens in a new tab) explains route ordering and fallback behavior. Keep external actions disconnected until both practice cases behave as expected.

Need an account? Start with Make Free (opens in a new tab). For the filter controls, see the beginner filter guide.