TL;DR: Auto-link items between two boards when something happens — item created, column changed, status changed, or item moved. Matching can use equals, contains, starts-with, and 2-column combinations. Pick the recipe that fits your trigger and your matching needs.
Category thumbnail — pending. Tracked in CONTENT-NEEDS.
When to use these automations
You want new items to auto-connect to their match on another board (no manual linking)
You want connections to fire only once an item reaches a specific stage
You want to react when an item is moved to this board from elsewhere
You need stricter matching using two column pairs to avoid false positives
Before you start
A Connect Boards column on this board, configured to point at the target board (see Setting Up Connect Columns)
A "matching key" column on each board (e.g. Email, SKU, Client ID) so the recipe can find the right pair
Matching logic decided in advance: equals (exact), contains (substring), starts with, ends with
Pick the recipe that fits your workflow
1. When an item is created, connect to a match
Recipe:"When an item is created, connect with connect column all/first items on another board where this column matches another column using this logic and this logic."
The most-used variant. New items auto-connect to their match on another board. Rank 2 in CSV usage. Also has a reverse variant (connect column on the other board) — covered inline on the leaf.
2. Match by 2 columns · When an item is created, connect
Recipe:"When an item is created, 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."
Stricter version — both column pairs must match before connecting. Use when a single column isn't unique enough. Reverse variant covered inline.
3. Match or create · When an item is created, connect
Recipe:"When an item is created, connect with connect column all/first items on another board where this column matches another column using this logic and this logic. If there's no match create a new item and connect."
Match-or-create fallback. Eliminates the "missing record" gap by auto-creating the target item if no match exists.
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."
Trigger is a column change, not item creation. Useful when the matching key isn't known until later. Reverse variant covered inline.
5. Match by 2 columns · When a column changes, connect
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."
Stricter column-change variant — both column pairs must match. Reverse variant covered inline.
6. Excluding a group · When a column changes, connect
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, excluding items in this group."
Adds a group filter — items in a specified group on the connected board are skipped. Keeps archived, done, or cancelled records out of new connections.
Recipe:"When status changes to something, connect with connect column all/first items on another board where this column matches another column using this logic and this logic."
Stage-gated variant. Items only link to the other board when their status hits the value you pick. Great for "Won → Delivery" or "Approved → Production" flows.
Recipe:"When an item is moved to this board from another board, connect with connect column all/first items on another board where this column matches another column using this logic and this logic."
Trigger is a cross-board item move (handoff). Ideal for intake / staging boards that receive items from other workflows and need to auto-link to a master record.