A Condition evaluates a Boolean expression and follows its True or False branch. Put the actions that depend on that result inside the appropriate branch. An action placed below the Condition runs after the control finishes and can therefore affect both paths. That location often explains an unexpected notification.
Use equals for a comparison and inspect the incoming types. Text '1' and numeric 1 are distinct. If the source contract says a quantity arrives as text, convert it explicitly before comparing the amount. A missing property needs its own policy; it shouldn't be treated as a confirmed approval. The checks exercise both paths, including a boundary case. Don't test only the event you expect to see most often. A rejection or zero-value request is part of the same flow.