Cross-board workflows

Cross-board workflows

TL;DR: Trigger actions on this board based on something happening to a connected item on another board. Sync status, move items to groups, or remove dependencies and connections. This category flips the direction — the trigger is on the other board, the action is here. For copying values, updates, dates, or names between connected items, see  Sync values between connected items .

When to use these automations

  • You want this board to react to changes on a connected board (incoming triggers)
  • You want connected item statuses, dates, or updates to drive workflow on this board
  • You want to clean up connections or dependencies based on lifecycle events on the other side

Before you start

  • Items must already be connected via a Connect Boards column on this board
  • For status-based recipes: the status column on the connected board (the trigger) needs to exist and be properly configured
  • For action-side columns: the destination column on this board needs to exist and match the recipe's expected type

What you can build

1. When connected status changes, sync status

When a connected item on another board has its status changed to a specific value, set this board's status column to a value you choose.
Use when: two boards represent the same work at different stages — engineering ticket → support ticket, fulfillment → sales order, content draft → publish queue.

2. When connected status changes, move to group

When a connected item on another board reaches a specific status, move the item on this board to a group of your choice.
Use when: the workflow on this board has stage groups that should follow the other board's progress automatically.

3. Cleanup: remove dependencies or connections on status change

When a status reaches "Done" or "Cancelled", automatically remove the dependency or the connection itself — keeps board relationships clean.
Use when: connections shouldn't linger after work is complete; old dependencies create noise in dashboards.

Common gotchas

  • The trigger is on the OTHER board. "When a connected item's status changes" fires on the linked board, not here. Easy to get backwards in setup.
  • One-to-many fires per match. If this board's item links to 5 connected items, an incoming trigger may fire 5 times. Test with a single connection first.
  • Removal recipes are not reversible. "Remove connection on status change" wipes the link permanently. Use carefully on production data.
  • Status labels are case-sensitive. The trigger value on the other board must match exactly.

Deep-dives

Dedicated recipe articles for each pattern coming in a follow-up pass. In the meantime, browse the full recipe library from the Automations Center → search "Connected Boards" → "All Automations".

Related

  •  Connect items across boards  — set up the connection first
  •  Connect + Sync  — auto-connect plus ongoing two-way sync (flagship combo)
  •  Sync values between connected items  — outgoing direction (push values from this board)

Still stuck?

Email  hello@fantasymedia.io  and we'll help you pick the right cross-board pattern for your workflow.