All templates
Flow ControlIntermediate
Use the OR Operator in Conditionals
Robomotion•Updated 9 months ago
Overview
Combines two conditions with a logical OR and branches the flow based on the result. Complements the AND-operator variant.
Use the OR Operator in Conditionals
Logical operators enable users to create complex logical expressions and implement advanced logic in their flows. For example, they can use the "OR" logical operator to create expressions that are true when at least one of the provided conditions is valid.
What Use the OR Operator in Conditionals can do
- Seed inputs (
Core.Programming.Function) —msg.tool = 'Robomotion'; msg.company = 'Some Other Corp';. - OR test (
Core.Programming.Function,outputs: 2) —return (msg.tool === 'Robomotion' || msg.company === 'Robomotion Inc.') ? [msg, null] : [null, msg];. - Port 0 shows
Core.Dialog.MessageBoxtitledFlow ran successfully!with bodyAt least one of the provided conditions was true.(optType: 'info'). - Port 1 goes straight to
Core.Flow.Stop(no else branch).
Behind the scenes
- Mirrors the AND tutorial; the only structural difference is
||vs&&inside the Function node. - Seeded values are deliberately mixed (one matches, one doesn't) to demonstrate that a single true operand is enough for the OR branch to fire.
More flow control templates
See all 7 →- Denial Worklist TriageWorks a clinic's denied insurance claims, choosing a different action for each denial code: fix and resubmit the ones missing a field the chart already has, write off what the payer will never cover, void duplicates of already-paid claims, and escalate the ones that need a human to call the payer. Waits for the resubmitted claims to be re-adjudicated, then reads each claim's real status back off the table and writes denial-actions.csv.
- Leave Request PolicingProcesses the pending leave requests in an HR system by policy: approves the ones that are clean and denies the ones that break a rule - an insufficient balance, an overlap with a teammate already off, or a request inside the month-end blackout - writing the reason into the required comment box. Brings only the edge cases to a human. Writes a decision CSV.
- Use Conditionals to Check if File ExistsChecks whether a given file is present on disk and routes the flow accordingly. A textbook conditional branching example.
- Use Labels to Check if File ExistsUses Label and GoTo to structure a loop that rechecks file existence — a non-sequential flow pattern useful for polling.
- Use Subflows to Check if File ExistsEncapsulates a "does this file exist?" check inside a reusable subflow so the main flow stays linear and readable.
- Use the AND Operator in ConditionalsShows how to branch a flow only when two conditions are both true using a Switch node with a combined predicate.