A scenario is what users create to connect different apps/services together via their corresponding modules in order to transfer and transform selected data. For more information, please visit the Creating a scenario section.
An app directly refers to an application or it can refer to a service. A service is a collective term for a source of bundles. A service may include a web API, web page, different types of servers (FTP, SMTP, IMAP), and etc.
When adding an app/service to a scenario, most likely you will have to first create a connection between Integromat and the app/service in order to retrieve or send the selected data. For more information, please visit the Connecting to services section.
Each app/service consists of different modules that define the way an app/service is to respond to a request. There are 4 types of modules: actions, triggers, iterators and aggregators. A scenario is comprised of a sequence of modules. For more information, please see the Types of modules sections.
A trigger is a module that allows you to grab bundles that were added or updated since the last run of a scenario. There are 2 types of triggers: scheduled and instant (webhooks).
A webhook is a special type of trigger that allows you to run a scenario immediately after a new bundle is available.
An action is a module that allows you to read or write bundles from or into a selected app/service.
A router allows you to duplicate data or add new routes to a scenario, so to re-route data and handle different groups of data separately. For more information, please see the Router and scenarios with multiple modules section.
An iterator is a type of module that allows you to take one bundle of data (an array of data) and divide into separate bundles.
An aggregator is a type of module that merges together multiple bundles (multiple arrays of data) into one single bundle.
A bundle is a basic unit that is returned or received by modules. A bundle consists of items.
An item is a part of a bundle. Bundles can consist of multiple items. There are several different types of items: text, number, boolean (yes/no), date, time, buffer (binary data), collections, select menu, array, and validation.
Filters are additional features that can be applied between two modules. A filter allows you to then only work with bundles that fit certain criteria. There are a number of different filters you can apply. For more information, please see the Filtering section.
ID is a name that is used to uniquely identify a bundle. An ID is usually used to differentiate a bundle that is to be updated or deleted from a given service.
An operation is a task performed by a module. For more information, please read the Counting the number of operations section.
Data transfer refers to the amount of data transferred through your scenario. For more information, please read the Account parameters section.
A data store is a tool that stores data from scenarios or allows to transfer data between individual scenarios or scenario runs. For more information, please read the Account parameters section.
A cycle refers to two phases of the scenario run – operation and commit. The scenario may consists of one or more cycles. For more detailed information, please see the Cycles article.
Integromat uses transactional processing to capture the scenario lifecycle. A transaction consists of several phases during which data is transformed from one consistent state into another consistent state. There are 4 phases: initalization, operation (reading or writing), commit/rollback, and finalization. For more information, please see the Transactions section.