Configure the Condition Node

The Condition Node lets a workflow make a decision and continue through different paths based on information that BotLance already knows. Instead of every contact following the same journey, you can check a field, tag, workspace value, or another supported condition and then send matching contacts through the Yes path while everyone else follows the No path.

For example, the Condition shown below checks whether the contact's Full Name equals John Smith. If the condition is true, the workflow follows the green Yes branch. If it is false, it follows the red No branch.

Inside the Condition editor, start by selecting a Field. You do not need to manually type variable names because BotLance gives you a searchable field picker containing the information already available to the workspace.

The picker is organized into System Fields, Custom Fields, Workspace, Tags, and Recommended. System Fields contain standard contact information understood by BotLance, such as names, email, phone, company, and country. Custom Fields are the fields created for your own business and may contain information such as budget, service preference, lead status, project type, or other values collected during the customer journey.

Workspace Fields are shared workspace-level values rather than information belonging to one particular contact. Tags let you branch according to whether a particular workspace tag is currently applied to the contact.

The Recommended area contains useful ready-made checks that BotLance can provide without requiring you to build the underlying logic yourself. For example, you can check whether the contact's email is already known. On supported Instagram workflows, BotLance can also provide a Follows your account condition so the workflow can branch according to the contact's current follow status.

After choosing the field, select the Operator that describes the comparison you want to make. BotLance only shows operators that make sense for the selected field instead of displaying every possible option.

For normal text fields, you can use comparisons such as equals, does not equal, contains, does not contain, is empty, and is not empty. Number fields can also use comparisons such as greater than, less than, greater than or equal to, and less than or equal to. Boolean values use true or false checks, while Tags simply use has tag or does not have tag.

Some operators do not require a separate value. For example, if you choose is empty, is not empty, is true, or has tag, the condition already contains everything BotLance needs to make the decision. When a value is required, enter it in the Value field beside the operator.

The example in the screenshot uses:

Full Name → equals → John Smith

When the workflow reaches this node, BotLance compares the stored Full Name against the configured value and chooses the appropriate branch.

A single Condition Node can evaluate several rules together. Select Add Condition to add another row, then configure its Field, Operator, and Value in the same way.

When multiple conditions are present, the Condition Logic setting at the top determines how BotLance combines them. Choose All conditions are true (AND) when every configured condition must match before the workflow follows the Yes branch. Choose Any condition is true (OR) when matching just one of the configured conditions is enough.

For example, an AND condition could require a contact to have a known email and carry a Qualified Lead tag before entering a particular branch. An OR condition could allow the same branch when either of two qualification rules is true.

Keeping several related checks inside one Condition Node is usually cleaner than creating a long chain of separate Condition nodes when they all belong to the same decision.

The Condition Node has two outputs on the canvas: a green Yes connector and a red No connector.

After configuring the condition, drag from each connector to the step that should run for that result. The Yes path is used when the configured logic evaluates as true, while the No path is used when it does not.

These branches can lead to any appropriate workflow step. For example, the Yes branch could send a qualified contact to a booking message while the No branch asks another question, sends different information, runs an Action, or continues through another Condition.

The Condition Node itself does not send a customer message or modify contact data. Its purpose is to evaluate the information available at that point in the workflow and decide which path should run next.

Conditions can evaluate information collected earlier in the same workflow. This works particularly well with the Data Collection Node. For example, a workflow can first ask for a customer's budget, save the answer into a Custom Field, and then use a Condition Node to decide which path should follow based on that value.

The same principle applies to System Fields, Tags, Workspace Fields, and values updated by other workflow Actions. As the workflow gathers or updates information, later Condition nodes can use that information for routing.

This allows you to build customer journeys where the path changes according to the data already available rather than sending every contact through the same fixed sequence.

A Condition Node works best when it represents one clear decision. You can combine several related rules using AND or OR, but avoid placing unrelated business decisions into one large condition simply because the editor allows multiple rows.

For example, a qualification decision might reasonably check budget, lead status, and an existing tag together. A completely separate question, such as whether the customer follows your Instagram account, may be clearer as another Condition later in the workflow if it controls a different part of the journey.

Once the Condition is configured and the Yes and No branches are connected, the workflow can automatically route each contact according to the information available when they reach that point.