List behavior, not just tools
Write one row for each automatic action you know about, including native provider filters and third-party rules. Name the responsible application, condition, consequence and owner. Do not put passwords, authorization tokens or message contents in the register. If you do not know whether an application acts automatically, mark that uncertainty. An incomplete but honest map is more useful than a confident list that omits an active participant.
Include an exception example
For each rule, describe a fictional wanted message that must not match. A rule for expired promotional announcements should not accidentally include an order confirmation you still need. This counterexample makes review concrete. If you cannot explain why the exception is excluded, simplify the condition or leave the task manual. A register is not an automatic protection mechanism; it is a way to expose unclear rules before they operate widely.
Review overlapping actions
Two rules can match the same message even if they live in different applications. Note that overlap and identify which result you expect. Do not assume execution order from the order of rows in your notebook. Check current product behavior where order matters. If the combined effect cannot be explained, pause the proposed addition and reduce the number of active layers before expanding automation across the account.
Keep a stopping route
Record where to pause or remove each rule and when it was last reviewed. Revisit the register after changing mail applications, adding an account or noticing unexpected mail movement. Archive old entries with a clear inactive label rather than losing the explanation of past behavior. The purpose is not paperwork for its own sake: it is to make a missing-message investigation and a later decision to stop using a service manageable.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Clean Email: Auto Clean overview — Merchant documentation · clean.email · Merchant-controlled · checked 2026-09-26
- Google: create rules to filter emails — Platform documentation · support.google.com · Merchant-controlled · checked 2026-09-26