Converger
This article describes alternatives and workarounds to a converger module, often requested by our customers.
Please note that there is no converger module available in . 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.
To implement the converger concept, use one of the following workarounds to avoid the duplication of the common sequence.
Add an extra filter-free route to the router to connect the common sequence (the one you would put after a converger module).
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 output 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, for example, MyKey.
Add a Data store > Get a record module at the beginning of the common sequence to obtain the previously stored data.
If you wish to avoid the use of the data store you can:
Use a JSON > Create JSON module followed by Tools > Set variable to store the resulting JSON in a variable (e.g. MyBundle).
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:
To avoid this, you may employ the ifemtpy() function as show below:
If there is a single value that you need to pass to the common sequence (e.g. ID), you can use the Tools > Set variable and Get variable modules.
also allows you to use the Set multiple variables module.
You may also place the common sequence to a separate new and then:
- Use the HTTP > Make a request module at the end of each route to pass the data to the new .
- Use the Webhooks > Custom webhook module at the beginning of the new to receive the data.