Your monday.com boards, mirrored with two-way sync
Boards and items stay in monday.com. Laya keeps a live, editable mirror on its own faster surface — drag items, change statuses, assign people and post updates, and every edit writes straight back through the monday.com API. Nothing is migrated.
Built around how monday.com boards actually work
monday.com teams model work in very different ways — Laya detects each board's model instead of forcing one on you.
Status columns or groups
Some boards track progress with a Status column, others use groups as kanban lanes. Laya reads whichever your board uses and mirrors its lanes accordingly — per board, automatically.
15 column types, editable
Status, people, dates and timelines, text, long text, numbers, tags, dropdowns, checkboxes, links, email, phone, country and hour columns are all readable and editable from Laya's side panel and inline editors.
Updates, without switching
Read an item's update thread and post replies straight from the Laya side panel — they land in monday.com as normal updates.
You stay in control of the mapping: a column-mapping drawer lets you choose exactly which status, people and date column drives each signal on the mirrored board.
What syncs — and in which direction
Edits made in Laya call the monday.com API immediately, with a per-item badge showing Queued, Syncing, Synced or Failed so you always know where a change stands.
| Data | monday.com → Laya | Laya → monday.com |
|---|---|---|
| Items | Yes — mirrored with their columns | Yes — create and edit real items |
| Status | Yes — Status column or groups | Yes — label change or group move |
| People (assignees) | Yes | Yes — each edit replaces the full set |
| Dates & timelines | Yes | Yes |
| Text, numbers, tags & more | Yes — 15 column types | Yes — the same 15 |
| Updates (comments) | Yes — read the thread | Yes — post from Laya |
| Subitems | No | No |
| Attachments | No | No |
One honest caveat: writing the People column replaces the whole set of assigned people on the monday.com side, so a simultaneous edit made inside monday.com can be overwritten. Full details live in the connect monday.com guide.
How fresh is the mirror — and what doesn't sync yet
We'd rather you knew the edges before you connect than discover them after.
- Subitems aren't mirrored or imported — subitem and progress columns are hidden.
- Priority, story points and issue type aren't carried over from monday.com.
- Attachments don't sync in either direction.
- Master-board imports from monday.com don't carry sprints — monday.com has no native sprint concept.
Hit a snag connecting? The monday.com connection troubleshooting guide covers the common failures and fixes.
One API token, scoped by the account you choose
monday.com connects with a personal API token — copy it from Profile → Developers → My access tokens in monday.com and paste it into Laya.
Least privilege, your way
The connection reads and writes as the account that owns the token. To keep access tight, connect with an account that can only see the boards you intend to mirror.
Encrypted at rest
Your token is stored encrypted and is never returned by any API response. monday.com tokens don't expire — they stay valid until you revoke them in monday.com, at which point a workspace Admin simply reconnects.
Admin-controlled
Connecting, mirroring and disconnecting need a workspace Owner or Admin. Disconnecting stops the sync but keeps your Laya boards — and your monday.com data is never touched.
Layer monday.com into one board with everything else
A master board pulls monday.com items in as native Laya issues alongside work from Jira, Azure DevOps, GitHub and GitLab — with a user-mapping step so items land assigned to the right teammates, and item updates carried across. Imported rows keep syncing: title, status and due date push back to monday.com, and title and status flow in. Read how it works in the master boards guide or compare per-provider coverage in what syncs per provider.
Free while Laya is in early access. Mirror your first board in minutes.