Sync Status Bidirectionally: Two-Way Cross-Board Sync Without Infinite Loops

Two-way sync sounds simple in theory: when Board A changes, update Board B. When Board B changes, update Board A. But there's a catch that makes this genuinely difficult — and it's why monday.com doesn't offer it natively.

The infinite loop problem.

Board A changes → triggers update on Board B → Board B has changed → triggers update on Board A → Board A has changed → triggers update on Board B → ...

Without loop prevention, you'd get an infinite cascade of automation triggers, burning through your automation quota in seconds and potentially corrupting your data.

The Problem

Cross-team workflows almost always need bidirectional sync. Consider these scenarios:

• Sales and Operations share a status that both teams update depending on who's acting. Sales marks "Ready for Ops", Operations marks "In Progress", Sales marks "Client Approved". Both boards need to show the current state.
• Development and Product track features on separate boards. Either team might update the status depending on the stage. Both boards need to agree.
• HQ and Regional offices maintain separate boards for the same projects. Updates can come from either side.

One-way sync only solves half the problem. If only Board A → Board B works, then anyone updating Board B directly creates a discrepancy. You need sync in both directions.

The Solution: Sync Status Bidirectionally

The recipe sentence:

"Keep a status in sync between this board and a connected board in both directions"

This is the advanced version of our one-way Update Status in Connected Board action. It syncs a status column between two connected boards in both directions, with built-in loop prevention.

When Board A's status changes, it updates Board B. When Board B's status changes, it updates Board A. And it does this without triggering an infinite loop.

How It Works (Loop Prevention)

The action includes internal state tracking that prevents cascading triggers:

1. User changes status on Board A
2. Automation fires → updates Board B
3. Board B's status has changed, but the action recognises this was an automation-driven change, not a user-driven change
4. The cascade stops. No loop.

This happens transparently. You don't need to configure anything for loop prevention — it's built into the action.

How to Use It

1. Install Community Cookbook from the monday.com marketplace
2. Set up the automation on both boards (Board A and Board B)
3. On each board: choose the Connect Boards column and the status column to sync
4. The bidirectional sync handles the rest

Real-World Use Cases

Cross-Team Project Tracking

Marketing and Engineering both track the same campaigns. Marketing updates "Content Ready", Engineering updates "Implemented". Both boards always show the same state.

Client and Internal Boards

You maintain a client-facing project board and an internal operations board. Status changes flow in both directions — clients see progress updates while your team sees client approvals.

Multi-Location Operations

Headquarters and regional offices manage the same initiatives on separate boards. Regardless of where the update originates, both boards stay synchronised.

Vendor Management

Your procurement board and your vendor's delivery board (if they also use monday.com) track the same orders. Status updates from either side propagate to the other.

One-Way vs. Two-Way: When to Use Which

| Scenario | Use | |---|---| | Updates always flow from one board to another | One-way (Update Status in Connected Board) | | Either board can be the source of truth | Two-way (Sync Status Bidirectionally) | | You need control over which direction syncs | One-way | | Multiple teams update the same status | Two-way |

Frequently Asked Questions

How does the loop prevention work?+

Do I need to set up automations on both boards?+

What if the two boards use different status labels?+

Can I sync more than two boards together?+