AFI
Is not empty
Is not empty passes when the chosen field carries any value at all. It takes no comparison value, so the value box disappears from the rule row when you select it.
When to use it
It is the most common guard in conditional logic: only send a contact to your CRM when an email address is present, only create a task when a description was filled in, only add someone to a phone campaign when they gave a number.
Reach for it whenever an optional field is required by the platform you are sending to. Blocking the integration is nearly always better than sending an incomplete record and cleaning it up later.
How to configure it
- Open AFI → Integrations and edit your integration.
- Switch on Conditional Logic.
- Pick the field and choose Is not empty. No value is needed, and the value box is hidden.
How it behaves
A field counts as empty when it arrives as an empty string, as nothing at all, or as an empty set of choices. Anything else passes.
That includes a field holding only spaces, and a field holding 0. Both have a value, so both pass Is not empty.
Quick reference
| Field value | Result |
|---|---|
na**@*****le.com |
Match |
0 |
Match |
" " (a space) |
Match |
| One checkbox ticked | Match |
"" |
No match |
| No checkboxes ticked | No match |
Example
A newsletter platform rejects records without an email address, and each rejection shows up in your AFI logs as a failed request.
Add a rule of {{email}} Is not empty to the integration. Submissions without an address never reach the platform, and the log stays clean.
Notes
If a whitespace-only value would count as blank for your purposes, pair this with a Does not match regex rule of ^s*$ and set the match mode to all.