Template di automazione per Flow Control

Works 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.

Processes 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.

Checks whether a given file is present on disk and routes the flow accordingly. A textbook conditional branching example.

Uses Label and GoTo to structure a loop that rechecks file existence — a non-sequential flow pattern useful for polling.

Encapsulates a "does this file exist?" check inside a reusable subflow so the main flow stays linear and readable.

Shows how to branch a flow only when two conditions are both true using a Switch node with a combined predicate.

Combines two conditions with a logical OR and branches the flow based on the result. Complements the AND-operator variant.