Match by 2 columns · When a column changes, connect
TL;DR: Stricter version of the basic "connect on column change" recipe — requires two column pairs to match instead of one. Use when a single column isn't unique enough to avoid false connections (e.g. multiple records share an Email, but Email + Account is unique).
What this does
Recipe: "When column changes , connect with connect column all/first items on another board where this column matches another column and this column matches another column using this logic and this logic."
Watches a column on this board. When it changes, the recipe searches the other board for items where two pairs of column values both match (using the comparison logic you pick). Connection only — no ongoing column sync.
The added strictness reduces false positives when one column alone isn't a reliable unique identifier.
When to use it
- Multi-tenant CRMs: match on Email AND Account ID to avoid linking the same email across different accounts
- Regional records: match on Company name AND Region/Country when the same company exists in multiple regions
- Product catalogs: match on SKU AND Variant when the same SKU is used across different variants
For the single-column-match version, use When a column changes, connect . For excluding items in a specific group on the other board, see Excluding a group · When a column changes, connect . For all connect variants, see Connect items across boards .
Before you start
- A Connect Boards column on this board, configured to point at the target board (see Setting up Connect Boards columns )
- The trigger column on this board
- Two matching key columns on each board that together uniquely identify a record
- Decide all/first behavior and comparison logic for each column pair
Set it up (4 minutes)
Untitled Video Guide
June 19, 2026 By Kevin - Customer Experience Manager
Finding the right automation recipe
1. Click Automate and search for "Connected Boards Automations"
2. Click on the "Connected Boards Automations" app
3. Find "When column changes , connect with connect column all/first items on another board where this column matches another column and this column matches another column using this logic and this logic".Click Use template.
4. Click the first column selector and select the trigger (e.g. Status).
5. Click "Status"
6. Click the with connect column selector, and choose the correct Connect Boards column that links this board and the target board.
7. Select either:1. all — allows an item to connect to multiple other items in the target board that match the condition.2. first — only connects an item to the first item in the target board that matches the condition.
8. Click the another board selector and choose the target board.
9. Click this column and select a column that will be used as one of the matching criteria. In most cases, our users select Name.
10. Click another column and select the exact same column type/name that you chose in the previous "this column" selector.
11. Click on the second this column selector, and select a column that will be used as the second matching criteria. (e.g. Project ID, Product ID, or even SKU number)
12. Click the second another column selector, and choose the exact same column type/name.
13. In the first this logic part of the recipe, select whether you want to connect an item to just 1 other item (Override existing connections), or multiple items (Add to existing connections).
14. Click the second this logic option. Most of our users choose "don't match empty values" so columns that are empty will not be used as a matching criteria.
15. Click "Create automation"
Testing the solution
16. Change the Status of an item to anything, and wait for the automation to connect the relevant items.
Reverse variant
Recipe: "When column changes, connect using the connect column on another board all/first items, where this column matches another column and this column matches another column using this logic and this logic. (Reverse)"
Same behavior as the standard recipe — match items by two column pairs and connect — but the direction is flipped. The connect column lives on the other board, not on this one. The recipe writes the link from the connected board back to this board.
Use it when the master record's board owns the connect column. All other fields and pickers work the same as the standard variant.
Common gotchas
- Both pairs must match — AND, not OR. For OR semantics, use two separate single-column recipes instead.
- Logic applies per pair. You can use different comparison logic for each pair (e.g. "equals" on Email, "contains" on Account ID). Pick deliberately.
- Triggers on every change of the trigger column. If that column is edited frequently, the recipe runs repeatedly. Pick a column that changes only when a meaningful re-link is needed.
- The connect column must already exist on this board. The recipe won't create one for you. (For the reverse variant, on the other board.)
Use this to dedupe. If your single-column-match recipe was creating noisy false connections, switching to a 2-column match usually cleans them up.
Next up
https://slite.com/api/public/notes/-_8c_fNocioReK/redirect
Excluding a group · When a column changes, connect
Related
- Connect items across boards (parent landing)
- When a column changes, connect — single-column-match version
- Excluding a group · When a column changes, connect — with group exclusion
- Match by 2 columns · When an item is created, connect — same matching, triggered on item creation
- Setting up Connect Boards columns — prerequisite
Still stuck?