Skip to main content

​
What This Node Does

The Intersect node finds and returns only the rows that exist in ALL input datasets. Use it to identify common records, validate data consistency across sources, or find overlapping data between tables. [SCREENSHOT: Intersect node with two input connections showing “Input A: 10,000 rows + Input B: 8,000 rows → Output: 3,000 common rows”]

​
When to Use This Node

Use the Intersect node when you need to:
  • Find common customers - Identify customers who exist in both CRM A and CRM B
  • Validate data consistency - Verify that production data matches test data for specific records
  • Find overlap between lists - Identify products in both “Active” and “Best Sellers” lists
  • Data quality checks - Confirm records exist in all required systems

​
Step-by-Step Usage Guide

1

Add Intersect node to canvas

2

Connect first input

Connect your first dataset to the Intersect node’s top input handle[SCREENSHOT: CRM A data connected to top input]
3

Connect second input

Connect your second dataset to the Intersect node’s bottom input handle[SCREENSHOT: CRM B data connected to bottom input]
4

Choose comparison mode

Select “Compare All Columns” (exact match) or “Compare Specific Columns” (match on selected columns only)[SCREENSHOT: Comparison mode dropdown]
5

Configure intersect type

Choose INTERSECT (remove duplicates) or INTERSECT ALL (keep duplicates)[SCREENSHOT: Intersect type dropdown]
6

Preview common rows

​
Tips and Best Practices

Specific Columns for Flexibility: Use “Compare Specific Columns” to match on keys (id, email) while ignoring columns that may differ (updated_at, status).
Standardize Data First: Use Rename and Convert nodes before Intersect to ensure column names and types match across inputs.
Case Insensitive for Names: Enable case insensitivity when comparing names, emails, or addresses to avoid missing matches due to capitalization differences.
Intersect for Validation: Use Intersect to confirm data synchronization between systems. Low row count indicates sync issues.
Combine with Except: After finding common rows with Intersect, use Except to find rows in Input 1 but NOT in Input 2 (missing records).
Test with Small Samples: Use Limit node on inputs to test Intersect logic with 100-1000 rows before running on full datasets.