Replacing Legacy Modules with New Modules

A majority of Integromat apps rely on external services, particularly on their APIs (Application Programming Interfaces). As the services evolve, so do their APIs. New API versions are being regularly released and legacy versions are getting deprecated and eventually shut down.

We closely follow releases of new API versions and implement new app versions based on the latest APIs.

To keep your scenarios running even after the shutdown of a legacy API, make sure to replace all the legacy (old) modules with new modules. 
Here is a step by step guide:

Step 1: Choose the scenario that is using legacy modules, and clone it to make a copy - make the new scenario.

  1. Navigate to the scenario Diagram.
  2. Open the Options drop-down menu in the top-right corner and select the Clone option.
    Cdpfrc7mWA.gif
  3. Change the name to distinguish between the legacy scenario and the new scenario and click the Clone button.
  4. The new scenario (still with the legacy modules) is created.

Step 2: In the new scenario you have created using the Clone function, choose the legacy module you want to upgrade to the new version, and click on the green upgrade arrows (2020-08-27_12_27_59-Integration_Google_Forms__copy____Integromat.png).

2020-08-27_12_25_13-Integration_Google_Forms__copy____Integromat.png

Step 3: Choose the corresponding new module from the list of modules.

The new module is placed in the scenario (not connected).

9qPh95BCmK.gif

For Google Forms, check this table to find a new counterpart of your legacy module:

Legacy Module New Module
Watch responses Watch Responses
Select responses Search Responses
Add a response Add a Response
Update a response Update a Response
Delete a response Delete a Response
  Search Responses (Advanced)

Step 4: Replace modules.

Triggers:

  1. Set the same field values in the new module as field values in the legacy module.
  2. Move the clock icon from the legacy module to the new module.
  3. Unlink the legacy module and link the new module to the desired module in your scenario.
    6rpWEQFT3T.gif

Other modules:

After adding the new module to the scenario (step 3 above), connect it after the legacy module.

ckbO1WlYjf.gif

Step 5: Set values in new modules.

We recommend opening the legacy scenario in a new browser tab to switch between the module's configuration faster.
NZj6LVksjS.gif
  1. Open the configuration of the new module.
  2. Switch to the tab with the legacy scenario and open the configuration of the legacy module.
  3. Copy and paste the content of each field from the legacy module to the new module (by switching between the legacy scenario and the new scenario tabs).
  4. Map needed values and select the options from drop-down menus.
  5. Set mapping in filters.
  6. If any items are missing in the mapping panel, please refer to our online documentation.
    YQoAcoMse4.gif

Repeat this for every module.

Step 6: Remove all the legacy modules from your new scenario and click Save.

oPeF6Uq8Rp.gif

 

Popular use cases from our blog

slack-automation-illustration

Slack Automation: 20 Free Templates to Get You Inspired

google-sheets-automation-alt

Google Sheets Automation for Ecommerce: 23 Free Templates

tweet-automation-illustration

How to Get Someone's Tweets Before Anyone Else Does

onboarding-automation-with-integromat-alt

How to Automate Employee Onboarding in Minutes with Integromat

shopify-order-to-manufacturer-illustration-alt

How to Auto Send Shopify Orders to Dropshipping Suppliers [Guide]

strava-exercise-to-google-sheets-illustration

Like a Champ: How to Save Strava Activities to Google Sheets

Didn’t find what you were looking for?

Ticket

Create a ticket

Contact our world-class support team and tell us what’s happening.

Create a ticket
Expert

Find an expert

We feature a network of 450+ certified partners across the globe who are ready to help

Find an expert

Automate any workflow in your business

Sign up for a free account today. No credit card required, no time limits on free plan.