One of the characteristics of Integromat is its transactionality, working similarly to relational databases. In practice, it means that each module contained in a scenario is processed in the following 4 phases:

  • initialization
  • operation (reading or writing)
  • commit or (rollback)
  • finalization

At the beginning of the scenario execution run, each module is initialized. During the operation phase that follows, the modules return bundles (Read operation) and/or perform other operations with the bundles (write operation). If the operation phase is successful for all modules, the third phase (commit) begins during which all operations performed by the modules are committed. If an error occurs during the operation or commit phase, all modules and bundles are rolled back (the operation or commit phase is aborted). The scenario run is then marked as Failed. If the third phase is successful, in the last step all modules are finalized and the scenario run is completed.

Scenario module lifecycle

The following text describes the individual phases in more detail.


During the initialization phase, all necessary connections (connection to a database, email service, etc.) are created. They are also checked if each module is capable of performing their intended operation(s).


Reading and/or writing is performed during the operation phase.

The reading operation consists of obtaining bundles that will then be processed by other modules according to a predefined scenario. An example of this is during the operation phase in the Dropbox module Watch files, Integromat returns new bundles (files) added since the last run of a scenario.

The writing operation activity consists of sending bundles to a given service for further processing. An example of this during the operation phase of the Dropbox module Upload a file, it uploads the received file to a selected Dropbox folder.


In this phase, operations are committed. This means that Integromat sends information to certain services about the successful execution of the scenario.


If an error occurs during the operation phase or the commit phase, Integromat starts the rollback phase on all modules. The rollback phase reverts everything to its initial state before the start of the run.

Some modules do not support rollback and data processed by these modules cannot be rolled back. For more information see the ACID modules section.


During the finalization phase, open connections (e.g. FTP connections, database connections, etc.) are closed and the scenario is completed.

ACID modules

All Integromat modules that support transactionality are marked with the ACID tag. The modules that are not marked with this tag do not support transactionality and cannot be reverted back to their initial state in case of error in other modules.

A typical example is the Send an Email action. Once the email is sent (during the operation phase), you cannot undo the sending.

Example: Transfer of bundles between databases

The following example shows how to connect three ACID modules. The aim of the below scenario is to get new rows from a MySQL database, insert (transfer) them into a MSSQL database and then insert the IDs of the rows from the MSSQL database into a PostgreSQL database.

When the scenario starts, the initialization phase is performed first. Integromat verifies connections to the MySQL, MSSQL and PostgreSQL databases one at a time. It everything goes well and the connections are successful, Integromat moves on to the operation phase. If an error occurs, the finalization phase starts instead of the operation phase and the scenario is terminated.

Next comes the operation phase. A preset procedure selects (reads) the table rows (bundles) from MySQL. Those rows are then passed to the next module that writes them to a selected table in the MSSQL database. If everything is in order, the last PostgresSQL procedure is called to insert the row IDs returned by the preceding module into the table.

If the operation phase is completed successfully, the commit phase begins. Integromat calls the SQL COMMIT command for each database and the write operations will be committed.

However, if the operation or commit phase fails due to an error, (e.g. connection failure), Integromat calls rollback. During the rollback phase, Integromat goes through all modules one after another and executes the SQL ROLLBACK command for each module to revert each database back to its initial state.

Finally, during the finalization phase, each module will close its connection to the database.


For each scenario, you can specify the maximum number of cycles allowed between the initialization phase and the finalization phase of the scenario execution run. By default, the maximum number of cycles is set to one. This can be changed in the Advanced scenario settings.

Example: In the above example, if you set the maximum number of cycles to 3, the initialization phase will run first followed by 3x the operation phase and 3x the commit phase and then will run the finalization phase.

Rate this article: