- Define fields and expected recipients
- Add a filter before the action it controls
- Check AND, OR and missing values deliberately
- Create the Router and name each rule
- Overlapping filters can produce several effects
- Separate route order from fallback matching
- Compare route results with a small acceptance list
- Leave a reason for every condition change
Define fields and expected recipients
Prepare practice rows containing request_id, category, amount and status. Send category=sales to sales, category=support to support, and other categories to review. Treat amount as a number. Distinguish a missing value from a literal zero or the text “none.” Write the expected destinations beside each example before configuring any modules.
Add a filter before the action it controls
Click the line between modules and set the filter name, mapped operand, operator and comparison value. For a new-intake-only workflow, compare the incoming status with new before the notification action. A bundle that fails the filter does not continue along that path. If exclusions need an audit trail, preserve their source IDs separately.
Check AND, OR and missing values deliberately
“Sales AND amount at least 10000” differs from “sales OR amount at least 10000.” Confirm the grouping shown by the editor. Include 9999, 10000, a blank amount and whitespace around the category in your practice cases. An Exists check alone does not prove that a value meets business rules; define valid categories and ranges too.
Create the Router and name each rule
Add Flow controls > Router and create sales, support and review branches. Place category=sales on the sales path and category=support on support. Name paths after their matching rule as well as their destination. This makes a later change easier to review because another operator can see why a record should have followed that branch.
Overlapping filters can produce several effects
Do not treat a Router as a first-match-only switch. If one route matches category=sales and another matches amount>=10000, a high-value sales record qualifies for both. Make the conditions mutually exclusive when exactly one owner is required. When sharing with several recipients is intentional, record that two notifications are the correct result for that example.
Separate route order from fallback matching
Router paths are processed sequentially. Reordering them does not remove an overlap in their conditions. A fallback handles data that does not fit the other routes. Use it to send an unfamiliar or missing category to review with its request ID. If the fallback has another filter, check that the added condition does not leave some records without any useful outcome.
Compare route results with a small acceptance list
In isolated destinations, check sales, support, unknown category, missing category and high-value sales records. Compare effects by request ID with the expected route list. A successful run can still exclude every bundle through filters. The examples here specify checks to perform; they are not measured execution results from a connected Make account.
Leave a reason for every condition change
Record the effective date and business reason for a change such as sharing high-value requests with a manager. To prevent repeat notifications during recovery, consider a processing key combining the request ID and destination. Review routing accuracy separately from delivery state: the right branch can still fail at its final action.
Start a small workflow in Make
Try the required workflow with practice data, then choose a plan around its usage and features. Check current prices, promotions and eligibility in the official signup flow.
Sign up on MakeAffiliate linkEstimate costs for your workload
Enter monthly jobs, billable steps and retries to see how different billing units affect your estimate.
Open cost calculatorOfficial sources
Pricing, availability and feature limits can change. Check the linked official pages before subscribing.
- FilteringInformation checked: 2026-10-29
- RouterInformation checked: 2026-10-29
- Scenario historyInformation checked: 2026-10-29
- Make pricing — Core at 10,000 monthly creditsInformation checked: 2026-10-28
- Make creditsInformation checked: 2026-10-26
- Make scenario settingsInformation checked: 2026-10-26