An aggregator is a type of module that merges multiple bundles into a single bundle.


An action is a type of module allowing reading/writing of bundles from/into a selected service. It is the most common, most general type of module.


An app represents a service or application. It consists of several modules.


Applying a filter on a specific route allows you to select bundles that meet specific criteria. For every filter, you can define any number of filter conditions. For more information please see the Filtering help guide.


ID is a name used to uniquely identify a bundle. Integromat usually requires the bundle ID for identification of the bundle to be updated or deleted from a given service.


A cycle trip begins with the initialization phase and ends with the finalization phase of a scenario execution run. For more information please read the Transactions help guide.


A module is a part of an app. It represents a task to be performed by Integromat. For more information please read the Types of modules help guide.


An operation is a task performed by a module. For more information please read the Counting the number of operations help guide.


An Iterator is a type of module allowing to divide arrays into separate bundles.


An item is a part of bundle. Every bundle contains several items. A Facebook post, for example, contains the following items: Author, Content, Date created, Date updated and the like.


A router allows to add a new route to a scenario. For more information please read the Router and scenarios with multiple modules help guide.


A scenario is a scheme defining the way in which the individual services shall communicate with each other. For more information please read the Creating a scenario help guide.


Service is a collective term for a source of bundles. Each service is represented in Integromat by an app. A service may include a web API, web page, different types of server (FTP, SMTP, IMAP) and the like.


Most apps require you to create a connection between Integromat and the account you have with a given service. For more information please read the Connecting to services help guide.


A trigger is a type of module that is always placed at the start of a scenario. It returns bundles added or updated since the last scenario run (according to settings).


Integromat uses transaction processing to execute a scenario. A transaction consists of several phases during which data is transformed from one consistent state into another consistent state.


A Webhook is a special type of trigger allowing to run a scenario immediately after a new bundle is available. For more information please read the Types of modules help guide.


A bundle is a basic unit returned or received by modules. Each bundle represents a different thing for each app. Examples include posts from Facebook, photos and videos from Instagram or tweets from Twitter.

Rate this article: