Conditions
Automations support a dedicated conditions system, separate from pricing rule conditions. These conditions are evaluated before any actions are executed.
Supported Condition Types
Conditions in automations follow the same structure as pricing rule conditions:
| Type | Description |
|---|---|
| Product | Match specific product IDs in the cart/order |
| Category | Match product categories in the cart/order |
| Tag | Match product tags |
| Quantity | Total quantity of items |
| Price | Product price ranges |
| SKU | Product SKU matching |
| Cart Total | Cart or order total threshold |
| User Role | Customer's WordPress role |
| User Meta | User metadata values |
| Segment | Customer segment classification |
| Coupon | Applied coupon codes |
| Country | Customer shipping/billing country |
| Shipping Zone | Shipping zone matching |
Match Modes
Automations use the same ALL/ANY match mode system:
- ALL — every condition must pass (default)
- ANY — at least one condition must pass
Evaluation Context
The conditions engine builds a context from:
- Cart contents (product IDs, categories, quantities, prices)
- User data (role, ID, email, meta)
- Order data (for
order_createdtrigger) - Shipping and country information
If conditions are not met, the automation is skipped and a "conditions_not_met" reason is logged.