What is the ANY node, and how does it route to different branches based on which condition turns true?

What is the ANY node, and how does it route to different branches based on which condition turns true?

The ANY node is a Conditions node in FYERS Automate that allows your automation to move forward through different branches based on which condition becomes true first. As soon as one condition inside the ANY node evaluates to true, the automation follows that specific branch and ignores the remaining conditions.

This node is useful when you want to react to multiple possible outcomes, but take action for only the first condition that occurs.

How the ANY node works

When you add an ANY node to the canvas and add multiple conditions inside it, FYERS Automate continuously evaluates all those conditions at the configured check interval. The moment any one condition becomes true, the automation immediately moves forward through the branch connected to that condition.

Each condition inside the ANY node has its own outcome path. The branch connected to the condition that turns true is executed, while all other branches are skipped.

How routing happens inside the ANY node

Every condition inside the ANY node is evaluated independently. When a condition evaluates to true, the automation follows the path connected to that condition’s output. If multiple conditions could eventually become true, only the first one that turns true is considered.

Once a branch is chosen, the ANY node does not wait for or evaluate the remaining conditions further during that run.

Simple example

Suppose you add an ANY node with multiple checks such as a price condition, a portfolio condition, and a time-based condition. If the price condition becomes true first, the automation immediately follows the branch linked to that price condition. Even if the other conditions turn true later, they are ignored for that run.

This allows you to build logic like: “Take action based on whichever event happens first.”

Note: The ANY node always selects only one branch per run. Once a condition inside it turns true, the remaining conditions are not evaluated further.



When should you use the ANY node?

  • When you want different actions based on different possible outcomes.
  • When multiple conditions can occur, but only the first one should decide the next step.
  • When building fallback or priority-based logic.
  • When you want to avoid waiting for all conditions to become true.

What If?

ScenarioWhat happens
One condition becomes trueThe automation follows the branch connected to that condition.
Multiple conditions become true at different timesOnly the first condition that turns true is considered.
A condition turns true after another branch is already chosenIt is ignored for that automation run.
I want the same action regardless of which condition becomes trueUse an OR condition instead of ANY.

Last updated: 22 Dec 2025