Two-Way Monday.com Board Sync with n8n for an Agency

Client context

Get Levrg runs client work on Monday.com with two views of the same work: client-facing boards that customers see, and internal boards where the team actually plans and executes. On top of that sit project boards that are meant to show the health of everything underneath them. I built this automation suite as part of my role as AI Automation Lead there.

The problem

The boards drifted apart constantly. A status updated on the internal board never reached the client board, or the other way round. When someone renamed or deleted an item on one side, its linked twin stayed behind as an orphan. Project boards rarely reflected the true state of the task boards, so anyone checking project health was reading stale information.

Keeping it all consistent meant someone reconciling boards by hand, which is exactly the kind of work that gets skipped on a busy week.

The automation I built

I designed an end-to-end automation suite in n8n, driven by Monday.com webhooks so changes propagate as they happen rather than on a polling delay. A second, scheduled automation keeps project and task boards aligned.

• Webhook-driven handling of item creation, updates, and deletions across linked boards
• Client update propagation, including user mentions, so the right people are notified on the board they actually use
• Bi-directional status synchronization through configurable mappings, so each board can keep its own status labels
• Dynamic movement of items across groups when their state changes
• Cascading renames and deletions, so linked items never become orphans
• Project and task board alignment with dynamic column and status label management
• Scheduled syncs, daily and every 6 hours, to keep portfolio views aligned with the task boards beneath them
• Real-time failure alerts to Slack

Design decisions that mattered

Two-way sync has one built-in trap: echo loops. When an update on board A is written to board B, board B fires its own webhook, which would write the same change back to board A, and so on. The design has to recognise changes the automation itself made and ignore them, and only act when the target value actually differs from the source. Getting this right is what separates a sync from a feedback loop.

Status mappings live in configuration rather than in the workflow logic. Client boards and internal boards rarely use the same labels, and teams change their labels over time. Keeping the mapping configurable means a board change is an edit to a mapping, not a rebuild.

Cascades need an order. A rename or deletion has to reach every linked item, and a deletion in particular should only cascade once the link between items is resolved, so nothing is removed from the wrong board. Real-time webhooks handle the immediate changes, and the scheduled syncs act as a safety net that brings project and task boards back into line on a fixed cadence.

Every failure goes to Slack straight away. A sync that fails silently is worse than no sync, because people trust the board and act on stale data.

Outcome

• Cross-board data consistency without manual reconciliation
• Project health tracking reflects reality, on a daily and 6-hour schedule
• Failures surface in Slack immediately instead of silently drifting

Stack