monday.com app v1 to v2 transition by May 1, 2026

we've released a new version of the monday com app in make here's what's changing and what you need to know what's changing? monday com is updating their api version, and we've released a new version of the monday com app in make to support it while we explored all options to maintain backward compatibility, this change requires an update to how the make monday com app works support timeline now through may 1, 2026 both v1 and v2 are available and fully supported after may 1, 2026 v1 will no longer be supported scenarios still using v1 modules may stop working or return errors who is affected? everyone using monday com you'll need to upgrade all your modules from v1 to v2 by may 1, 2026 if your scenarios use specific modules with mapping changes, you'll need to update your mappings before or during the upgrade see below to check if this applies to you not using monday com? no action needed do your modules have mapping changes? before you upgrade, check if you're using any of these affected modules if not, skip to the upgrade steps affected module type 1 discontinued fields modules list boards, get a board what changed these fields no longer exist border , var name , done colors , color mapping , labels position v2 , hide footer what you do remove mappings that reference these fields affected module type 2 timestamp renamed modules get & list get an item, get an item's column value, list board's items, list group's items search search items in the board by column values, search items in the board by column values (advanced) watch watch board's items (poling trigger), watch board's items by column values, watch group's items, watch board’s column values, watch item's column value what changed changed at timestamp is now updated at what you do remap any mappings using changed at to use updated at instead how to upgrade step 1 replace your v1 modules in the scenario builder, look for the green upgrade arrow on your monday com modules click it, then select "show me new modules" to upgrade to v2 step 2 update affected mappings (if applicable) for any modules listed above, find and remove or remap the discontinued or changed fields step 3 test your scenarios run your scenarios to ensure they work correctly tip speed up your migration you can use the https //help make com/make devtool to speed up your migration use the swap variable function to update mappings more efficiently across multiple modules instead of editing each one individually where to learn more technical documentation docid\ mj qahlkwgsr o ecoyif