AutomationConditionsInput
Automation rule conditions support both simple comparisons and complex logical groupings with unlimited nesting.
Simple Condition Example
{
"key": "orders.dynamic_field",
"configuration": {
"field": "order_total",
"operator": "greater_than",
"value": 100
}
}
Logical Group Example
{
"logical_operator": "AND",
"conditions": [
{
"key": "orders.dynamic_field",
"configuration": {
"field": "order_total",
"operator": "greater_than",
"value": 100
}
},
{
"key": "orders.tags",
"configuration": {
"operator": "includes_any",
"value": ["premium", "vip"]
}
}
]
}
Complex Nested Example
{
"logical_operator": "AND",
"conditions": [
{
"key": "orders.dynamic_field",
"configuration": {
"field": "order_total",
"operator": "greater_than",
"value": 500
}
},
{
"logical_operator": "OR",
"conditions": [
{
"key": "orders.tags",
"configuration": {
"operator": "includes_any",
"value": ["gold"]
}
},
{
"key": "orders.auto_fulfill",
"configuration": {
"operator": "equals",
"value": false
}
}
]
}
]
}
Important Notes
- For simple conditions: Use
keyandconfiguration - For logical groups: Use
logical_operatorandconditionsarray - The
NOToperator requires exactly one condition in the array - Conditions can be nested to any depth for complex business logic
- Available condition keys depend on the selected event type
- Configuration structure varies by condition type
input AutomationConditionsInput {
conditions: [AutomationConditionsInput!]
configuration: JSON
key: String
logicalOperator: LogicalOperatorEnum
}
Fields
AutomationConditionsInput.conditions ● [AutomationConditionsInput!] list input
Nested conditions for logical group
AutomationConditionsInput.configuration ● JSON scalar
Condition-specific configuration parameters
AutomationConditionsInput.key ● String scalar
Component key for simple condition
AutomationConditionsInput.logicalOperator ● LogicalOperatorEnum enum
Logical operator for condition group
Member Of
AutomationConditionsInput input ● RegisterAutomationInput input ● UpdateAutomationInput input