When a column changes, connect
TL;DR: When a specific column changes on this board, this recipe searches another board for matching items and connects them through a connect column. Connection only — no ongoing sync. Use when the matching key isn't known at item creation and only gets populated later.
What this does
Recipe: "When column changes, connect with connect column all/first items on another board where this column matches another column using this logic and this logic."
Watches a specific column on this board. When its value changes (filled in for the first time, edited, or replaced), the recipe scans the other board for items where a matching key value matches, using the comparison logic you pick. If matches are found, the connection is written to your connect column. You also choose whether to link all matching items or just the first.
Connection only — no ongoing column sync.
When to use it
- Item was created without a matching key, gets a Client ID added later → connect at that moment
- Account Name is updated to canonical form → re-link to the master record
- External system writes a Reference ID to this board → connect to the source record
For stricter matching on two columns, use Match by 2 columns · 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 (the one whose change should fire the recipe)
- A matching key column on each board with values that overlap
- Decide all/first behavior and comparison logic
Set it up (3 minutes)
1. Open the Automations Center
From your board, click Integrate.
2. Search Connected Boards Automations
Search Connected Boards and pick Connected Boards Automations.
3. Find the recipe
Find the recipe "When column changes , connect with connect column all/first items on another board where this column matches another column using this logic and this logic." Click Use template.
4. Pick the trigger column
The column field is the one whose change fires the recipe (e.g. Status, Date, Owner, etc).
5. Pick the correct "Connect Boards" column
Click "connect column" and select the Connect Boards column which links this board to the target board.
5. Select either All or First.
Decide whether this automation will connect ALL items that match the condition, or just the FIRST item that matches.
5. Select the target board
Click "another board" and choose the target board where the matching items live.
6. Determine the match criteria
Fill this column (matching key on this board) and another column (matching key on the connected board).
In most cases, users select Name as the match criteria/condition. The automation will then work on items/subitems that have the exact same name. You can also use another column as the match criteria such as a Task number, or SKU, or Project ID or any unique identifier.
Make sure to select the exact same element when selecting the "another column" value. You can also choose to match the item's name Name with the other item's Text column — and if their values match, the connection will be established.
7. Choose how to handle multiple connections (this logic)
Pick Override existing connections to replace, or Add to existing connections to keep and append.
8. Choose how to handle empty values (this logic)
Pick Match empty values or Don't match empty values (usually the latter).
9. Click Create automation
Reverse variant
Recipe: "When column changes, connect using the connect column on another board all/first items, where this column matches another column using this logic. (Reverse)"
Same behavior as the standard recipe — match items by column value 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.
Test that it works
On an item on this board, change the trigger column to a value you know matches an item on the other board.
Open the connect column and confirm the link appeared.
Change the trigger column on another item to a value that doesn't match anywhere — confirm no link is created.
Common gotchas
- Triggers on every column change. If your trigger column is edited frequently (e.g. Notes), the recipe will run repeatedly. Pick a column that changes only when a meaningful re-link is needed.
- Override mode wipes existing connections. If you have manually-added connections on the connect column, "Override" will replace them. Use "Add" unless you specifically want to clear stale links.
- Logic mismatch. Whitespace, capitalisation, formatting differences kill "equals" matches. Use "contains" for fuzzy joins.
- 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 for "lookup later" patterns. When the matching key isn't known at item creation (e.g. external systems fill it in async), this trigger is the right fit instead of "on item creation".
Next up
https://slite.com/api/public/notes/H7FfSwlFA3K7b6/redirect
Match by 2 columns · When a column changes, connect
Related
- Connect items across boards (parent landing)
- Match by 2 columns · When a column changes, connect — stricter matching
- Excluding a group · When a column changes, connect — with group exclusion
- When an item is created, connect to a match — same connect pattern triggered on item creation
- Setting up Connect Boards columns — prerequisite
Still stuck?