In Automate, OR, AND, and IF are condition nodes that continuously check current data while an automation is running. These nodes are designed for logic where Automate keeps evaluating whether something has become true or false over time.
Some triggers work differently. They are event-based, meaning they complete their role only once, at the exact moment a specific event happens. Because of this difference in behaviour, not every trigger can be used inside OR, AND, or IF conditions.
OR, AND, and IF do not wait for one-time events. Instead, they repeatedly evaluate their connected conditions during the automation run.
AND continues checking until all connected conditions become true.
OR continues checking until any one connected condition becomes true.
IF evaluates a condition and routes the automation based on whether the result is true or false.
For this repeated evaluation to work correctly, the conditions inside these nodes must be something Automate can evaluate continuously over time.
The ANY node behaves differently from OR, AND, and IF. Instead of repeatedly evaluating conditions, the ANY node waits for multiple events in parallel.
As soon as one event occurs, the automation proceeds through that path and ignores the remaining events for that run. Because of this behaviour, the ANY node is suitable for triggers that are meant to happen only once.
A Range Breakout completes the moment price moves outside the defined range.
A Price Breakout completes when price crosses the specified level.
A Webhook trigger completes when the webhook is received.
A Wait time completes once the waiting period ends.
An Orderbook status trigger completes once the selected order reaches the chosen status.
Use OR, AND, or IF when you want Automate to keep monitoring values like P&L, positions, or symbol data — when the condition may become true at any point during the run and when the logic needs continuous evaluation.
Use the ANY node when you want to act based on an event that happens only once, when you want the automation to proceed based on whichever event occurs first, and when the trigger should not be evaluated again after it completes.
Last updated: 14 Dec 2025