FAQ

We do not currently provide support over the phone. You can contact our support team using our Open ticket form. You may also search our Help section to find the answer to your issue.

Data transfer refers to the amount of data transferred through your scenario. Suppose, you have a scenario that retrieves a 100kB image from FTP and reduces its size to 50kB and saves both images to Dropbox. The amount of data used in this scenario is 150kB. The data moved between modules is counted only once, regardless of the number of modules deployed. The amount of data you have available depends on the subscription you have purchased.

A connection is the link between your Integromat account and the third-party service you want to use. The connection can be easily created when editing a scenario. To add a connection, click the Add button in the module setting and follow the step-by-step instructions.

An operation is any task performed by a module. Every time a trigger runs, it is considered one operation. Every time an action performs a task, it is counted as one operation. Suppose, for example, you have a scenario that will retrieve 2 new images from DropBox and post them to Google Photos and Facebook. Executing this scenario will require 5 operations (1x Dropbox 2x Google Photos + 2x Facebook). The number of operations performed during a scenario run can be found under History. The number of operations you have available depends on the subscription you have purchased. For detailed information on how to count the number of operations click, here.

Performing a check is one of the most expensive operations in Integromat. Unlike most integration services, Integromat executes runs in transactions. But to start a transaction, we first need to check and make sure everything is up and running. What this means is, we need to initialize every module in the scenario and open all the connections. We do this so we can keep the possibility of an execution fail to a minimum. The initialization process, in many cases, is more expensive than the rest of the execution.

Another reason why we charge for check operations is that nowadays, most of the services out there are supporting webhooks. If you don’t know what a webhook is, you can imagine it as a cellphone. Instead of repeatedly calling your favorite shop to see whether the goods you ordered are in the store, you can instruct the shop to call you once the products arrive. In Integromat language, the difference between regular trigger and an instant trigger (webhook) is the same. With webhooks, we're waiting for the 3rd party to give us a call.

A scenario defines a sequence of steps to be executed by Integromat. For each scenario, you specify the data source, how the data is to be processed, and what data is to be used and what is to be ignored. Integromat lets you create as complex of scenarios as you need; even the most sophisticated scenarios are possible.

All registered users have access to the same Integromat features. The free Integromat account though, has free usage limits. It has a set number of operations (the number of times Integromat executes your scheduled tasks) and an allotted amount of transferred data. After you have explored building automated workflows on the free plan, choose a subscription based on your needs.

We do our best to ensure that Integromat modules support all features currently available for a given third-party application. Nevertheless, if there are any features that you find missing in Integromat, please let us know by opening a ticket.

Please check our list of supported apps. If you don't see the app you are looking for listed, you can suggest its integration (please, open a ticket). Advanced users can use our HTTP and JSON apps to connect to almost any service. For more information, please read here.

Common scenarios are run at intervals according to the schedule you specify (e.g. every hour, every 5 minutes, once a month, and the like). There are special triggers, called instant triggers (webhooks), that can start your scenario immediately after they receive data from a given service. Instant triggers can be extremely useful. We recommend to use them whenever possible. They help to reduce the number of operations. Received data is processed immediately without waiting for the next scheduled run. For example, the Paypal module Watch payments will start your scenario immediately after a payment is received.

You can use as many modules as you want in a scenario. You can create independent routes and specify which data should flow through them. You can also use results returned by individual actions and then pass them on to the next action.

Integromat uses profile pictures from the Gravatar service.

To switch from using a Google account, you need to create a password first. In the login page, click the "Lost password" link and follow the procedure of resetting the password. Once you reset your password, you should be able to log in via email/password.

Agreggators merge data into one single collection. An example of this is, files being compressed into a zip archive and sent as an email attachment.

If you use the Email module Retrieve attachments, each attachment will be sent individually through the rest of the modules in the scenario. Similar modules are also available in other apps that receive multiple files at once.

Yes, Integromat works with files. Using Integromat, files can be received, saved, transformed, converted, encrypted, etc. Moreover, Integromat provides a wide range of built-in features designed to enable users to work effectively and creatively with the data contained in the files.