We are currently preparing for the Monday API version upgrade, and we’re facing a challenge with the deprecation of the older Monday modules in Make.com.
The main issue is the upgrade process. As far as I understand, the only option is to manually replace each deprecated Monday module with the new version inside every scenario. This may be manageable for a small number of scenarios, but it becomes very time-consuming at scale.
In our case, we have over 1,000 Monday modules across multiple client scenarios, so replacing them one by one would require a significant amount of time.
How is everyone handling the upgrade of Monday modules on Make.com?
Is there a way to automate the process, or is there a more efficient method to update them in bulk?
As of now, there is no automated method available to replace the deprecated monday module. The transition needs to be handled manually by updating the affected modules within the scenario.
You will need to remove the deprecated module and reconfigure the appropriate replacement module, ensuring that all necessary fields, mappings, and settings are properly adjusted to maintain the workflow functionality.
If you need any implementation support kindly contact us
I suggest using AI to modify blueprints of scenarios that you can download from Make.com. Once modified, you can re-upload the blueprint with only the monday.com modules fixed. This way, you don’t manually have to replace every module or re-map all of the impacted modules and filters and such that live downstream. Keep in mind that you will have to make sure your trigger module has the same scheduling - when you upload blueprints, the scheduling always defaults back to “At regular intervals”. But you should not have to reconnect the webhook if it’s a webhook trigger - just the scheduling.