AFI
Not between
Not between is the inverse of Between (inclusive). It passes when a numeric field sits outside the range you type, at either end.
When to use it
Reach for it when the interesting submissions are the ones at the extremes: order totals that are unusually small or unusually large, lead scores outside a normal band, quantities that fall outside a standard pack size. One rule covers both tails, where Greater than or Less than would only cover one.
How to configure it
- Open AFI → Integrations and edit your integration.
- Switch on Conditional Logic.
- Pick the numeric field, choose Not between, and type the range as two numbers separated by a comma.
A value of 100,500 matches everything below 100 and everything above 500.
How it behaves
The range parses exactly as it does for Between: comma or pipe separator, surrounding spaces ignored, reversed order normalised.
The end points are excluded from the match, because they are inside the range. With 100,500, a submission of exactly 100 does not pass.
If the field value is not a number, or the range is malformed, the rule fails and the integration does not run. Not between does not get a free pass on a broken configuration just because it is a negative test.
Quick reference
| Range | Field value | Result |
|---|---|---|
100,500 |
99.99 |
Match |
100,500 |
100 |
No match |
100,500 |
500.01 |
Match |
500,100 |
750 |
Match |
100,500 |
abc |
No match |
Example
An operations team wants a Slack alert for orders that look anomalous, meaning under £10 or over £5,000, while leaving everything ordinary alone.
Set the rule to {{order_total}} Not between 10,5000 and point the integration at the alerts channel.
Notes
Because a non-numeric value fails the rule, submissions with a blank amount will not trigger a Not between integration. If you also need to catch missing values, add an Is empty rule on a second integration.