Branches your workflow into True and False paths based on comparing one field’s value against another field’s value. Unlike Basic Condition (which compares against static values), this node compares fields dynamically at runtime.Documentation Index
Fetch the complete documentation index at: https://docs.bondata.ai/llms.txt
Use this file to discover all available pages before exploring further.
Configuration
| Setting | Description |
|---|---|
| Left Field | The first field to compare |
| Operator | Comparison operator (equals, not equals, greater than, less than, etc.) |
| Right Field | The second field to compare against |
How It Works
Select the left field
Choose the first field - this can be from any entity or virtual field in your workflow.
Output
| Output | Description |
|---|---|
| True | Records where the comparison is true (e.g., field A > field B) |
| False | Records where the comparison is false |
Example
Route records where HubSpot and Salesforce have different company names:- Left Field: HubSpot.Company.Name
- Operator: not equals
- Right Field: Salesforce.Account.Name
- True path → flag for data quality review
- False path → records are consistent, continue normally
Best Practices
- Use this node when comparing two dynamic values - use Basic Condition for static value comparisons
- Ensure compared fields have compatible types (don’t compare a string to a number)
- This is especially useful for cross-system data validation
Related Nodes
- Basic Condition - branches based on field vs. static value comparison
- Router Condition - routes to multiple paths based on different conditions
- Simple Filter - filters records instead of branching