Two-Way Sync Between monday.com Boards: Where Connect Boards and Built-In Automations Stop, and How to Build One That Holds

2. What monday.com does natively, and where it stops

Marketplace sync apps fill part of the gap and are worth a look when you need the same item shown on a few boards with little logic. They get harder to justify when you need different labels per board, cascades, updates with mentions, and alerts when something fails.

3. What a real two-way sync has to handle

• Different labels on each board. The internal "Waiting on QA" might be "In review" on the client board. The sync needs a mapping, in configuration, both ways.
• Creation in either direction. A request created on the client board creates its internal twin, linked, in the right group.
• Renames and deletions that cascade. Rename or delete one side and the twin follows, so nothing is left as an orphan.
• Updates and @mentions. A client comment reaches the internal team on the board they use, mentioning the right person, without anyone writing it twice.
• Group moves. When work changes state, the item moves to the matching group on the other board.
• Roll-ups. Project or portfolio boards reflect the task boards beneath them.
• Scale and boundaries. Hundreds of boards, more items than linkage limits allow, and boards in other workspaces or another company's monday.com account.
• Real columns. Synced values that people can sort, filter, group, use in formulas and dashboards, and trigger native automations from, which mirrors cannot always do.
• No echo loops. A change written by the sync must not bounce back.
• Missed events. Webhooks are retried for a while, then dropped. Something has to catch what was missed.
• Alerts. A failed sync has to tell someone, because people trust the board.

4. How I build it: webhooks, n8n, and the GraphQL API

1. Webhooks on both boards. monday.com sends events for column changes, name changes, item creation, moves, archives, deletions, and new updates (webhook events). Each event goes to an n8n workflow, which answers monday's challenge request when the webhook is registered.
2. A record of which items are twins. For a few boards, a Connect Boards column, so people can still click through. When an account has too many boards or items for linkage limits, or the boards sit in different accounts, the pairs live in a mapping table that the sync owns instead.
3. Values written into real columns. Each board keeps its own Status, Date, People, and Numbers columns, filled by the sync, so sorting, filtering, formulas, dashboards, and native automations work on every board.
4. Mappings in configuration. Status labels, group names, and which columns sync in which direction live in a mapping, not in workflow logic. Changing a label is an edit, not a rebuild.
5. Two loop guards. All writes come from a dedicated integration user, and events made by that user are ignored. Before writing, the workflow reads the target and skips the write if the value already matches.
6. One mutation per item. Writes go through change_multiple_column_values, so an item is never left half-updated, and the workflow stays inside the API's complexity budget.
7. A scheduled safety net. monday retries a failed webhook every minute for 30 minutes. A scheduled reconciliation, for example every 6 hours, compares linked pairs and fixes anything that drifted.
8. Alerts to Slack. Every failure posts the item, the board, and the error to a channel someone reads.

For the API side in detail (authentication, pagination, column value formats, and the webhook challenge in n8n), see using the monday.com GraphQL API with n8n.

5. What this looks like in production

I built this for an agency running client-facing boards, internal boards, and project boards on top of them. Before, boards drifted constantly: statuses changed on one side only, renamed or deleted items left orphans behind, and project boards were rarely current. The sync suite now handles creation, updates, and deletions across linked boards; carries client updates across with user mentions; syncs status both ways through configurable mappings; moves items between groups; cascades renames and deletions; and realigns project and task boards on daily and 6-hour schedules, with failures posted to Slack. Nobody reconciles boards by hand anymore. The full write-up is in the two-way board sync case study.

6. When you do not need a custom sync

• One board only needs to see a few values from another: use Connect Boards and a Mirror column.
• One-way creation, such as a won deal creating a project: a built-in "create item in board" recipe is enough.
• The same item shown on several boards with identical values and little logic: try a marketplace sync app first.

Go custom when you need label mapping, cascades, updates and mentions, roll-ups across many boards, more boards than Connect Boards allows, sync across workspaces or accounts, or the confidence that a failure will be noticed.

Frequently asked questions