Types of modules

Integromat distinguishes five types of modules: Actions, Searches, Triggers, Aggregators and Iterators . The two latter ones are intended for advanced scenarios.

Actions

Actions are the most common type of module.

  • A typical action module returns just a single bundle which is then passed on to the next module for processing.
  • Action modules can be placed at the beginning, middle or end of a scenario.
  • Scenarios can contain an unlimited number of action modules.

Examples:

Update

The Action type has got four sub-types: Create, Read, Update and Delete. The Update sub-type have been designed to enable the following three operations:

  1. Erase the content of a field. This operation takes place when the content of the field is evaluated to erase keyword (not to be confused with empty):
  2. Leave the content of a field unchanged. This operation takes place when the field is left empty or the content of the field is evaluated to empty (represented via null in JSON):
    mceclip0.png
  3. Replace the content of a field. This operation takes place in all other cases than those two described above.
If you do not see the erase keyword in the mapping panel than either the module is not an update module or it has not been updated to the latest apps specification yet.

The reason, why it has been decided that empty will result in no change of the field content is that if there is a need to act differently and erase the field instead then it is easily achievable with the following formula:

mceclip0.png

whereas leaving the content of the field unchanged when the field's content is evaluated to empty is currently not possible.

Searches

  • A typical search module returns zero, one or more bundles which are then passed on to the next module for processing.
  • Search modules can be placed at the beginning, middle or end of a scenario.
  • Scenarios can contain an unlimited number of search modules.

Examples:

Triggers

Trigger modules generate bundles when there has been a change in a given service. The change can be a creation of a new record(s), deletion of a record(s), update of a record(s), etc. Integromat distinguishes between two types of triggers: Polling triggers and Instant triggers.

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

Polling triggers

Polling triggers are designed to regularly poll a given service whether there has been a change since their previous run. So you will typically schedule a scenario containing a polling trigger module to run periodically by selecting for example At regular intervals option from the Schedule setting panel. If there is a change the trigger will return bundles containing information about the change. If there is no change the trigger will output no bundles.

Polling triggers allow you to select the first bundle they should output via the epoch panel. The panel is displayed automatically after you save a trigger or when you make a substantial change in the trigger settings. You can also display the panel by right-clicking the module and choosing "Choose where to start" from the context menu.
NOTE: Settings made in the epoch panel affect only the first execution of the module. Once the module is executed, it will remember the last outputted bundle and the settings made via epoch panel will be voided.

Examples:

Instant triggers

Instant triggers enable the service to notify Integromat about the change  immediately. You will typically wish to schedule a scenario containing an instant trigger to run immediately by selecting the Immediately  option from the Schedule setting panel. See also Webhooks for further details on how the incoming data are handled.

Examples:

Aggregators

Aggregator is a type of module that accumulates multiple bundles into one single bundle.

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

Examples:

Iterators

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

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

Examples:

Popular use cases from our blog

tracking-testimonials-article-integromat

How to Automatically Collect Customer Testimonials [Tutorial]

automate-lead-routing-integromat-article-illustration

Automated Lead Routing: 3 Solutions for Busy Sales Teams

use-case-integromat-eventbrite-illustration

How to Promote Events on Twitter Like an Automation Ace

trello2

How to Automatically Turn Tweets Into Inspiring Images [Tutorial]

part4

How to Automate Procurement in Your Shopify Store - Part 4

part3

How to Automate Procurement in Your Shopify Store - Part 3

Didn’t find what you were looking for?

Ticket

Create a ticket

Contact our world-class support team and tell us what’s happening.

Create a ticket
Expert

Find an expert

We feature a network of 450+ certified partners across the globe who are ready to help

Find an expert

Automate any workflow in your business

Sign up for a free account today. No credit card required, no time limits on free plan.