One Workflow, Many Paths
Conditional routing workflows branch based on field values, subsidiary, amount, or custom logic. Different records take different paths—different approvers, different actions, different outcomes—within a single workflow.
Step 1: Define Your Branches
Document the routing logic: if amount < $1K route to manager; if $1K–$10K route to director; if > $10K route to CFO. Or: if subsidiary = US do X; if EU do Y. Create a workflow with multiple transitions from the same state.
Step 2: Add Transitions with Conditions
From a single state, create multiple transitions. Each transition has a condition. The first transition whose condition is true will fire. Order matters—put the most specific conditions first.
Step 3: Assign Different Actions per Branch
Each branch can have its own actions: different approvers, different emails, different field updates. Use "Initiate Approval" with a different approver lookup per branch.
Common Routing Use Cases
- Route POs by amount to different approvers
- Route bills by department or vendor type
- Route orders by customer segment or geography
- Route journal entries by account type
Get in touch for workflow design that handles complex routing logic.