Router
In Make, a router splits the scenario into several chains of modules. Each route processes the data according to a condition defined in the filter. The routes run in order and not in parallel, and you can define a fallback route that handles data that did not match any other route.
On this page
Source content checked . English translation published 2026-10-27.
In business automation
Sometimes a scenario needs to behave differently depending on the type of data that reaches it. In Make, a router splits the scenario into several chains of modules, and each route processes the data according to a condition defined in the filter. The routes run in order and not in parallel, and you can define a fallback route for data that did not match any other route.
Examples
These examples illustrate a possible workflow. Adapt the connections and rules to your own systems.
Splitting leads by source
A scenario receives leads from different sources. A router splits it into two routes, and each route has a filter that checks the lead's source, so each lead passes to the chain of modules that suits it.
A fallback route for data that did not match
A router has routes with defined conditions, and a new item does not meet any of them. A fallback route handles this data, so that it is not lost without anyone noticing.
Relevant tools
- Make
- The definition comes from the Make Help Center, which describes the router and the fallback route.
What to check
- Thinking the routes run in parallel. According to Make's documentation they run in order.
- Not defining a fallback route, so data that did not match any condition is not handled.