Converger

This article describes alternatives and workarounds to the Converger module, which is often requested by our customers. 

Please note that there is no Converger module available in Integromat. At the moment, it is just a concept that provides a counterpart to the Router module, allowing you to reduce duplication of modules in different routes.

Usage

In some cases, the routes after the Router module might contain completely identical sequences of modules - a common sequence:

In this case, you could use a Converger module to merge the two (or more) routes into one and connect the common sequence after it:

Workarounds

To implement the Converger concept, use one of the following workarounds to avoid the duplication of the common sequence.

Data store

  1. Add an extra filter-free route to the Router to connect the common sequence (the one you would put after a Converger module).
  2. Add Data store > Add/replace a record modules at the end of each Router's route (except the new extra route) to store the data outputted by the modules on the route that should be passed to the common sequence. The Data store would contain just one record, the record's key can be e.g. "MyKey".
  3. Add Data store > Get a record module at the beginning of the common sequence to obtain the previously stored data.

JSON

If you wish to avoid the use of the Data store you can:

  1. Instead of the Data store > Get a record module use JSON > Create JSON module followed by Tools > Set variable to store the resulting JSON in a variable (e.g. "MyBundle").
  2. Instead of the Data store > Get a record module use Tools > Get variable to obtain the previously stored variable followed by JSON > Parse JSON.

Please note that if no route is executed, the JSON > Parse JSON will throw the following error:

mceclip1.png

To avoid this, you may employ the ifempty() function as show below:

mceclip2.png

A variable

If it is just a single value that you need to pass to the common sequence (e.g. ID), you can employ only the Tools > Set variable and Get variable modules.

A separate new scenario

You may also place the common sequence to a separate new scenario and then:

  1. Employ HTTP > Make a request module at the end of each route to pass the data to the new scenario.
  2. Employ Webhooks > Custom webhook module at the beginning of the new scenario to receive the data.

Popular use cases from our blog

automated-data-collection-crm-illustration

How to Automate Data Collection - Part 5: CRM Systems

automated-data-collection-chatbot-marketing-illustration

How to Automate Data Collection - Part 4: Chatbot Marketing

automated-data-collection-paid-ads-illustration

How to Automate Data Collection - Part 3: Paid Ads

automated-data-collection-email-illustration

How to Automate Data Collection - Part 2: Email Marketing Segmentation

personalized-customer-experience-illustration-integromat

5 Automated Solutions to Personalize Customer Experience

data-collection-automation-forms-pt-1

How to Automate Data Collection - Part 1: Online Forms

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.