Configuration
How It Works
1
Select the left field
Choose the first field - this can be from any entity or virtual field in your workflow.
2
Choose an operator
Select how to compare the two fields (equals, greater than, etc.).
3
Select the right field
Choose the second field to compare against.
Output
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