Skip to main content

Replacing Legacy Modules with New Modules

A majority of Make 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 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:

  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.

  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

  3. Choose the corresponding new module from the list of modules. The new module is placed in the scenario (not connected).

    9qph95bcmk.gif

    1. 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)

  4. Replace modules.

    1. 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

    2. Other modules:

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

        ckbo1wlyjf.gif

  5. Set values in new modules.

    Note

    We recommend opening the legacy scenario in a new browser tab to switch between the module's configuration faster.

    nzj6lvksjs.gif

    • Open the configuration of the new module.

    • Switch to the tab with the legacy scenario and open the configuration of the legacy module.

    • 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).

    • Map needed values and select the options from drop-down menus.

    • Set mapping in filters.

    • If any items are missing in the mapping panel, please see Mapping.

      yqoacomse4.gif

    • Repeat this for every module.

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

    opef6uq8rp.gif
In this section: