# Condition (entry)

**Condition (entry)** checks a Gravity Forms entry and routes the run to **Yes** or **No** based on whether its conditions were met.

## When to use it

Use it when the next step depends on an entry value, such as plan, approval status, delivery method, or payment choice.

## Settings

![Condition entry settings comparing the upstream Gravity Forms Email field with a fictional address](/documentation/flowcrafter/screenshots/node-condition-entry-settings.png)

| Setting | What it controls |
|---|---|
| **Form source** | The form whose fields appear in the rule builder. This is usually detected automatically. |
| **Entry source** | The upstream entry to check. `$input` uses the current entry; a flow tag or query-result selector can choose another. |
| **Conditional logic** | One or more field rules. Choose whether all rules or any rule must match. |

:::tip[Need more powerful conditions?]
[GP Advanced Conditional Logic](https://gravitywiz.com/documentation/gravity-forms-advanced-conditional-logic/) adds multiple Any/All rule groups, date and time rules, user-aware conditions, formulas, and extra comparison operators. Use it when your decision needs a combination of rule groups or more than a field-value comparison.
:::

## 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 each field, operator, expected value, current value, and result.

## Good-to-knows

- **Entry source** selects which entry to check. When this node runs, it fetches that entry again and checks its latest saved field values, not an older copy passed along by another node.
- Changes made while a workflow is queued or paused affect the decision. For example, an updated approval status determines the branch when the run reaches this node.
- If the entry has been deleted or can no longer be loaded, the node stops with an error rather than deciding from outdated data.

## Example

After **[Form Submitted](/documentation/flowcrafter/nodes/triggers/form-submitted/)**, add a rule where *Membership* **is** `Pro`. Connect **Yes** to the Pro welcome email and **No** to the standard welcome email.

![A membership workflow routing Pro members and other members to different welcome emails](/documentation/flowcrafter/screenshots/condition-entry-example.png)