Files
plunk/apps/wiki/content/docs/automation-patterns/conditional-branching.mdx
T
2025-12-07 13:36:31 +01:00

47 lines
1020 B
Plaintext

---
title: Conditional Branching
description: If/then logic in workflows
icon: GitBranch
---
## Overview
Conditions split workflows into two paths based on contact data.
```
[Condition: plan = "premium"?]
├─ True → [Premium email]
└─ False → [Upgrade offer]
```
## Operators
| Operator | Example |
|----------|---------|
| `equals` | `plan equals "pro"` |
| `notEquals` | `plan notEquals "free"` |
| `contains` | `email contains "@company.com"` |
| `greaterThan` | `mrr greaterThan 100` |
| `lessThan` | `loginCount lessThan 5` |
| `exists` | `company exists` |
| `notExists` | `lastName notExists` |
## Nested conditions
Chain for multi-tier logic:
```
[Condition: enterprise?]
├─ True → [Enterprise email]
└─ False → [Condition: pro?]
├─ True → [Pro email]
└─ False → [Free email]
```
## Tips
- Store numbers as numbers, not strings
- Check field exists before comparing
- Limit to 3 levels of nesting
- Test both paths