Help

Types of modules

Integromat distinguishes 4 types of modules that differ mainly with regard to what data they process: actions, triggers, aggregators and iterators. The two latter ones are intended for advanced scenarios.

Action

An action is the most common, most general type of module.

  • Every action can return one or more bundles which are then passed to the next module for processing.
  • Actions can be placed at the beginning, middle or end of a scenario.
  • Every scenario can contain an unlimited number of actions.

Examples of actions

  • The Dropbox action Upload a file package sends a file to a selected Dropbox folder and returns its identificator.
  • The Image action Resize receives an image, resizes it to specified dimensions and passes the resized image to the next action.
  • The Google Analytics action Create a report gets information about web traffic and passes it on for further processing.

Trigger

A trigger is a module which is able to return bundles that were newly added or updated (depending on the settings) since the last run of the scenario. Integromat distinguishes two types of triggers: scheduled and instant triggers (webhooks).

Whereas scheduled triggers ask periodically a given service whether there are new bundles placed at disposal, in case of webhooks (kb://webhooks.html), the service notifies Integromat as soon as there are new bundles available. You can schedule a scenario containing webhooks to run immediately by selecting the Immediately option from the Schedule setting panel.

  • Every trigger can return one or more bundles which are then passed to the next module for processing.
  • Triggers can be placed only at the beginning of a scenario.
  • Every scenario can contain only one trigger.

Examples of triggers

  • The Dropbox trigger Watch files returns files that were newly added since the last time the scenario was run.
  • The Twitter trigger Watch Tweets returns Tweets posted by the user since the last time the scenario was run.
  • The Tumblr trigger Watch posts returns new posts added to a selected blog since the last time the scenario was run.
  • The Paypal trigger (webhook) New notification returns new payment notifications. If you schedule a related scenario to run Immediately, it will be executed immediately after receiving a notification.

Aggregator

An Aggregator is a type of module that composes multiple bundles into one bundle.

  • Every aggregator returns only one bundle which is then passed to the next module for further processing.
  • Aggregators can be placed only in the middle of a scenario.
  • Every scenario can contain an unlimited number of aggregators.

Examples of aggregators

  • The Archive aggregator Create an archive compresses received files to a zip archive.
  • The CSV aggregator Aggregate to CSV merges multiple strings from a scv file into a single row.
  • The Tools aggregator Compose a string combines several strings together into a single string.

Iterator

An iterator is a type of module that splits arrays into multiple separate bundles.

  • Every iterator returns one or more bundles which are passed to the next module for processing.
  • Iterators can be placed only in the middle of a scenario.
  • Every scenario can contain an unlimited number of iterators.

Example of iterators

  • The Email iterator Retrieve attachments breaks an array of attachments into separate bundles.
Rate this article: