Condition (data)

Condition (data) compares flow tags or plain values from earlier steps. It does not require a Gravity Forms entry.

When to use it

Use it for API responses, webhook payloads, query counts, AI output, or any decision based on step output rather than entry fields.

Settings

Setting	What it controls
Conditions	One or more rules, each containing a source value, an operator, and a target value. Either value can be a flow tag or literal text.
Match	Whether all rules or any rule must match.

Core operators are is, is not, greater than, less than, contains, starts with, and ends with.

Need more powerful data comparisons?

GP Advanced Conditional Logic adds multiple Any/All rule groups and extra operators such as is in, does not contain, and fuzzy matching. Use it to combine groups of comparisons over your step output or match values more flexibly.

Output and branches

• Yes runs when the configured logic matches.
• No runs when it does not.
• result is yes or no.
• logic_type is all or any.
• rules records the resolved values, operator, and result for each comparison.

Good-to-knows

• An unresolved flow tag remains as its literal {{ ... }} text instead of becoming blank. Test both branches with representative output so missing runtime paths are obvious.

Example

To branch on whether a query found registrations:

1. Add Get Entries and configure the form and filters.
2. In Condition (data), compare the Get Entries count flow tag with 0 using greater than.
3. Connect Yes to Send Email and include the count in a registration summary.
4. Connect No to Add Entry Note to record that no matching registrations were found.