Add a Switch (Condition) Node

A Switch (Condition) node is a workflow component that evaluates one or more conditional expressions against your workflow data and routes execution down different branches depending on which condition(s) match. It enables branching logic inside QuoteCloud so you can direct approvals, tasks, or notifications to different paths based on field values, variables, or outputs from earlier nodes.

Use a Switch Condition node whenever your process must take different actions based on changing data or outcomes. Common scenarios include routing by approval status (approved/rejected), pricing tiers, customer type, validation results, or calculated values generated earlier in the flow.

This is especially helpful in sales quoting software and sales proposal software workflows where quotes or proposals require different approval chains, notification recipients, or follow-up steps depending on the quote size or customer segment.

The node evaluates each defined condition—typically expressions that reference workflow fields, variables, or previous node outputs. When a condition evaluates to true, the workflow follows that condition's associated branch. You can define multiple exclusive branches to map specific values or ranges to different processing paths, letting the engine pick the matching branch at runtime.

Define a default or fallback branch to handle cases where no specific condition matches; the workflow will follow the default when no condition is met. If no default branch exists, behavior depends on the workflow engine's settings and may result in the workflow stopping, logging an unmatched state, or raising an error—check your workflow engine logs and settings to confirm the configured behavior.

Yes. Conditions can reference data produced by earlier nodes—field values, computed results, and outputs from document generation steps. In QuoteCloud this includes values used in quote and proposal documents and data synchronized from connected systems (for example, accounting fields synced via QuickBooks integration). This lets your quote software or proposal software drive branching based on real runtime data.

When building the Switch node, add a clearly labeled default or fallback branch and connect it to the steps that should run when no other condition matches. Make sure the default branch is reachable in the editor and that any downstream steps include error handling or notifications so unmatched cases are visible in logs and dashboards.

Write clear, maintainable expressions and prefer explicit comparisons (e.g., ranges or exact matches) rather than ambiguous checks. Keep conditions mutually exclusive when you need a single path, or define a priority order if multiple conditions might be true. Add a default branch to catch unexpected values, and include logging or notifications so you can trace why a particular branch executed. These practices reduce errors in sales quoting software and proposal software flows.

Test each branch using representative workflow payloads that exercise your different conditions (different pricing tiers, customer types, approval outcomes). Use the workflow engine's tracing or debug mode to step through evaluation and inspect the values used by each expression. Add temporary logging nodes or notifications to confirm which branch executed. This approach helps validate routing logic in quote software and proposal software scenarios before you deploy to production.