🟣 Monday app transition from v1 to v2

News
1

Hey Makers :waving_hand:

We have released a new version of our Monday app. Read the info below to find out what’s changing! :down_arrow:

Monday.com is updating their API version and we’ve released a new version of the app in Make to support it. You’ll need to upgrade all your Monday modules from v1 to v2 by May 1, 2026 to ensure your scenarios work. If you’re using specific modules with mapping changes, you will need to update the mappings as well.

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.


:arrow_up: 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.


:hourglass_not_done: What is the timeline

  • Until May 1, 2026 both v1 and v2 versions are available and supported in the scenario editor.
  • After May 1, 2026 the v1 version will no longer be supported and therefore scenarios using this version may stop working or return errors.

:books: Read more about the update in our Help Center

1 Like
2

Hi Vendy,

Thank you for the detailed announcement.

We are currently reviewing a large number of existing scenarios that use monday.com v1 modules, and we would like to better understand the real level of risk involved.

Specifically, could you clarify the following points:

  1. If a scenario uses v1 modules but does not rely on any of the discontinued or renamed fields, will those modules continue to function after May 1, 2026?
    In other words, is the risk limited strictly to modules that use affected mappings, or is there a broader compatibility concern?

  2. After May 1, 2026, when v1 is no longer supported, does that mean:

    • v1 modules will be technically disabled and stop executing entirely,

    • or they may continue running but without maintenance and guarantees,

    • or they will continue working correctly?

  3. Is the migration to v2 strictly mandatory for all monday.com modules, regardless of mapping usage, or is it primarily recommended to avoid potential future instability?

Given the operational impact of updating a large number of production scenarios, understanding whether this is a hard technical requirement versus a best-practice recommendation would help us plan appropriately.

Thank you in advance for the clarification.

3

Hello @simabbrescia :waving_hand:

Thank you for your questions! We absolutely understand that while using a large number of Monday modules, upgrading might take a while. So, to answer your questions:

  1. Monday updated their API version, and after May 1, 2026, the v1 version will not be supported. Please upgrade all your modules, regardless of the mappings and fields, as mentioned in our documentation, so all your scenarios work as expected.
  2. As mentioned, the v1 version will no longer be supported, and scenarios using v1 modules may stop working and return errors.
  3. To ensure your scenarios continue to work, please upgrade your modules accordingly.

Thank you!