All templates
Flow ControlBeginner
Use Conditionals to Check if File Exists
Robomotion•Updated 9 months ago
Overview
Checks whether a given file is present on disk and routes the flow accordingly. A textbook conditional branching example.
Use Conditionals to Check if File Exists
Implementing different logic paths based on specific conditions is essential to most automation scenarios. Conditionals enable users to check values and run different blocks of code depending on the result.
What Use Conditionals to Check if File Exists can do
- Input Dialog titled
Check if file exists, messagePlease populate a file name to check if it exists in your desktop folder., defaultFileName->msg.user_input. - Branch on cancel (
Core.Programming.Function,outputs: 2) — empty input short-circuits toCore.Flow.Stop. - Build path (
Core.Programming.Function) —msg.candidate_path = global.get('$Home$') + '\Desktop\' + msg.user_input. Core.FileSystem.PathExistsonmsg.candidate_path->msg.exists(boolean).- Branch on existence (
Core.Programming.Function,outputs: 2) — port 0 buildsmsg.dialog_text = "Filename: '<name>' exists in your desktop folder."and showsCore.Dialog.MessageBoxtitledFile found!; port 1 builds the "doesn't exist" message and showsFile not found!.
Behind the scenes
msg.user_inputis just a filename, not a full path — the flow prepends the Desktop directory (global.get('$Home$') + '\Desktop') before the existence check. Preserve the path join exactly.- Cancelling the input dialog short-circuits everything; no "cancelled" dialog is shown.
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 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.
- Use the OR Operator in ConditionalsCombines two conditions with a logical OR and branches the flow based on the result. Complements the AND-operator variant.