Add a Switch (Condition) Node
This guide shows you how to add a switch (condition) node in a QuoteCloud workflow, allowing you to create conditional paths and manage approvals based on different scenarios.
Steps to add a switch node
Understand the purpose of a switch node
A switch node works similarly to a trigger node, but instead of starting the workflow, it controls the workflow path by checking conditions.Add a switch node
In the workflow editor, click the node placeholder beneath your existing workflow step and select Switch .Review the generated condition nodes
After adding the switch node, the workflow automatically creates two child condition nodes: one for matched conditions and one fallback condition path.Identify the switch node
The diamond-shaped node represents the switch controller that manages how conditions are evaluated in the workflow.Configure the first condition node
Click the first condition node labelled If the condition is met to define how the switch node should control the workflow.Understand the fallback condition
The second condition path acts as the automatic fallback route. If none of the configured conditions are met, the workflow will follow this default path.Open the Add Condition panel
When you select the condition node, the Add Condition panel will appear on the right side of the screen.Configure the workflow condition
Define the condition using the available fields and comparison operators. For example, you may configure a condition where Total Value is greater than 100 .Apply the condition settings
After defining the condition, click Apply to activate the condition node within the workflow.Add additional condition nodes
To expand the switch node with more conditions, click the circular plus icon beneath the existing condition node.Configure additional conditions
Configure any new condition nodes the same way as the first condition node, then click Apply to save each condition.Understand condition order
When the workflow reaches a switch node, it checks the child condition nodes from left to right and follows the first condition node that evaluates as true.Complete the workflow setup
Once your conditions are configured, the switch node will control the workflow automatically based on the conditions you defined.
FAQs
What is a Switch (Condition) node in a QuoteCloud workflow?
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 to direct approvals, tasks, or notifications to different paths based on field values, variables, or outputs from earlier nodes.
When should I use a Switch Condition node?
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 quote size or customer segment.
How does the Switch Condition node evaluate and route conditions?
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 or map value ranges to different processing paths so the engine picks the matching branch at runtime.
What happens if none of the defined conditions match?
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 you don’t provide a default branch, behavior may vary depending on how the workflow is configured, so it’s best practice to always include a fallback path to avoid unexpected stops.
Can conditions use data from previous nodes, documents, or external integrations?
Yes. Conditions can reference data from earlier nodes, document fields, workflow variables, and external integrations that surface values into the workflow. This lets you route based on calculated values, document metadata, or synced information from connected systems.
Can I create multiple exclusive branches or overlapping conditions?
You can create multiple branches that map specific values or ranges to different processing paths. For predictable results, design conditions to be mutually exclusive or ensure you have a clear rule for priority (for example, a specific branch plus a fallback). Clear, non-overlapping conditions reduce ambiguity in routing.
How do I test or debug a Switch Condition node?
Test a Switch node by running the workflow with representative input values and verifying that each condition’s branch executes as expected. Use logging or workflow run history to inspect the evaluated expressions and outputs. If a branch doesn’t run, check the referenced fields/variables and confirm the expressions are correctly formed and receiving the expected data.
Best practices for building conditions in QuoteCloud workflows
Keep expressions simple and readable, reference named fields or variables instead of ad-hoc values, and include a default/fallback branch. Use mutually exclusive conditions when possible and document the intent of each branch. These practices improve maintainability and help ensure your sales quote or proposal flows perform reliably in QuoteCloud's quote software and proposal software environments.