> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.meetgail.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.meetgail.com/_mcp/server.

# Conditional

> Sends a run down different paths based on a list of conditions.

The Conditional node is a fork in the road. It checks a list of conditions in
order and sends the run down the path attached to the first one that is true. If
none are true, the run follows the default path. Each path can lead to a
completely different set of steps.

## When to use it

* You need the workflow to do different things for different cases, such as
  high-value versus routine accounts.
* You want mutually exclusive routes with a catch-all fallback for everything
  that does not match.
* You want to branch on the result of an earlier step, like a
  [Check](/platform/workflows/node-reference/logic-and-flow/check) outcome or a score.

If you only need a single labeled verdict rather than separate paths, reach for
[Check](/platform/workflows/node-reference/logic-and-flow/check) instead.

## Inputs

| Field        | What it's for                                                                                 | Example                                               |
| ------------ | --------------------------------------------------------------------------------------------- | ----------------------------------------------------- |
| Branches     | An ordered list of conditions, each with its own path. The first condition that is true wins. | `Decision is APPROVED` leads to the issue-policy path |
| Default path | The path the run takes when no branch condition is true.                                      | Send to a manual-review path                          |

Branches are checked top to bottom, and only the first matching branch runs.
Conditions are written as [expressions](/platform/workflows/core-concepts/expressions/using-expressions-in-nodes)
that read values from earlier steps.

## Outputs

The Conditional node produces no value of its own. Its job is to choose which
path the run follows next.

## Example

An agency routes inbound quote requests based on the decision an earlier
[Check](/platform/workflows/node-reference/logic-and-flow/check) step produced. The
Conditional node has two branches: if the decision is `APPROVED`, the run goes
to the path that issues the policy; if it is `NEEDS_REVIEW`, it goes to the path
that assigns a reviewer. Anything else follows the default path, which notifies
the customer that more information is needed.

![The Conditional node configuration panel, showing branches with labels and condition expressions.](https://fdr-prod-docs-files-public.s3.us-east-1.amazonaws.com/gail.docs.buildwithfern.com/150903c84b8ea31819dbdaabcbcbf653578238447a194a471af23cf9590ac72c/docs/pages/platform/workflows/assets/logic-and-flow-conditional.png?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Content-Sha256=UNSIGNED-PAYLOAD&X-Amz-Credential=AKIA6KXJSKKNFOCF7G4B%2F20260823%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20260823T232903Z&X-Amz-Expires=604800&X-Amz-Signature=5a95ca9fdf86b7fb08f8e236979870e400260b56bff7bf63edb28c59332c524a&X-Amz-SignedHeaders=host&x-amz-checksum-mode=ENABLED&x-id=GetObject)

Order matters. Because only the first matching branch runs, put the most
specific condition at the top and let broader conditions fall below it.
Anything that should always be caught belongs in the default path.

## Related nodes

#### [Check](/platform/workflows/node-reference/logic-and-flow/check)

Produce a single labeled outcome instead of branching the run.

#### [For Each](/platform/workflows/node-reference/logic-and-flow/for-each)

Repeat a set of steps for every item in a list.