Two monday.com boards edited from both sides, kept in step without echoing
Five Make scenarios keep a production company's job board and its directors' boards in step in both directions: a new job on either side creates its twin, an edit on either side updates it, and new shoot-day subitems follow. Each direction ignores the changes the other wrote, so the boards never ping-pong.
Where this applies
Production companies, agencies and any team that keeps one master board and a board per person or client, with both sides editing.
- updates in four weeks, no errors
- 639+
- sync paths: create and update, each way
- 4
- scenarios, items and subitems
- 5
The problem
A production company keeps a master board of jobs, while each director works from a board of their own. Both are edited: the office changes dates and details on the job, a director updates their copy. Unless the two agree, someone is working from stale information.
One-way sync is easy and the wrong answer here. Two-way sync has a well-known trap: an update from board A writes to board B, which fires B's change event, which writes back to A, and the boards trigger each other indefinitely. And the boards are not laid out the same, so columns have to be mapped, not copied.
What we built
Four paths, not one scenario
There is a scenario for each direction and each kind of change: create from the job board, create from a director's board, and update from either side. Each is small enough to read on its own, and one failing does not stop the others.
Wait for the board to settle
The update scenarios pause after the change event before reading the item, so monday.com's own automations on the board finish first and the scenario reads the final values rather than a half-updated row.
Map, don't copy
A set-variables step maps the job board's columns onto the director's board, which is laid out differently, and the linked item is updated only when it exists.
No echo
Each direction filters out the changes the other direction wrote, so an update that arrived from the sync is not sent back. That is what stops a two-way sync from becoming a loop.
Subitems follow
A further scenario copies new subitems (shoot days, deliverables) from a job to the director's copy: it waits, finds the twin of the parent, creates the subitem and fills its columns, with an ignore handler on each column update so one bad value does not lose the rest.
The outcome
All five scenarios are live, built in April and May 2025. The update from the job board to the directors' boards ran at least 639 times between 24 September and 21 October 2026, without an error.
Where it stops
Updates rely on the link between an item and its twin, so an item created outside the sync has no twin to update. The pause is fixed, so a slow board automation could still be read half-way through. Subitem edits, and subitems created on a director's board, have scenarios of their own that are not described here.
Built with
- Make.com
- monday.com
Patterns used
- One scenario per direction
- Wait for the board
- Echo filter
- Column mapping
Page copy drafted with AI assistance. Skofi is accountable for it. Editorial policy
Have something shaped like this?
If any part of the above resembles a problem you are living with, a short call is the fastest way to find out whether it is the same problem underneath.
What happens on the call
- 15 minutes, no deck
- We map the process on the call
- A written scope, or an honest no