The detail that matters: A Get Contact step runs before every write, with a skip node after Create. The flow looks for an existing contact first. That is what keeps the database clean a year later, when nobody remembers how it was set up.

The detail that matters: Filters sit on the router and read the status field, so every branch is independently testable — you can prove one path works without firing the other.

The detail that matters: It watches rows, not the file. A file-level trigger fires on any edit, including someone fixing a typo; a row-level watch only fires on genuinely new entries, so the alerts stay worth reading.