Here you pay what it costs - just like with electricity and water!
Our solutions are primarily developed and operated in the make Entreprise platform.
Here, the current cost is calculated according to a concept called "operations".
Here we review what that means.
How to calculate number of operations in Make
Make calculates the total number of operations that the modules in your scenario perform. The more modules and the more packages (data records) processed in a scenario means a higher number of operations.
What you pay for your scenarios therefore depends on how complex your scenarios are.
Definition of operations:
Each time a module in a scenario performs an action, it counts as an operation. For example, when a scenario reads
a record from Uniconta, typing a row into a Google sheet, or sending an email, each action counts as one operation.
How to count the number of operations
Each time a module in a scenario performs an action, it counts as one operation.
The first module in a scenario runs only once, and it always counts as one operation (even if it doesn't return a packet). The number of times the remaining modules run depends on the number of packets they need to process (one run of a module per packet).
More examples of what counts as operations:
• Reading data from an app or webhook
• Search for data in an app
• Creation of data in an app
• Updating data in an app
• Deleting data from an app
• Transformation of data using the built-in tools
• Aggregation of a series of data into an array or text
• Iteration of a series of data
An exception is the aggregator module, which is counted as one operation per set of packets being processed.
Note
There are a few exceptions of modules where Make does not count the operations.
Error handling modules (Rollback, Break, Resume, Commit, Ignore)
Router module
The Sleep module uses operations but does not consume data.
Example: Connect Instagram to Dropbox
The following scenario connects Instagram, Image and Dropbox package modules. It shows how to download photos from a selected Instagram account, resize them, and upload them to a selected Dropbox folder.
When the execution of a scenario is complete, Make displays the number of actions performed by each module in the small white circle above the module.
In the above example, the Instagram module returned three images and performed an action. Each of the three images then passed through the image size module. Three additional actions were needed to resize them. Finally, each image was uploaded to the Dropbox folder. To upload three different images, the module had to run three times (ie three additional actions). The execution of this scenario required a total of seven actions (1 + 3 + 3).
Experienced specialists
Flows takes care of the configuration of your integration through experienced specialists who have a thorough understanding of the systems used.
best practices
With Flows, you achieve an integration that meets the overall standards in handling data, and which at the same time offers a clear and easy-to-understand overview.
Right on target
At Flows, we do not complete the process until your integration has been fully tested and you have confirmed that the result is satisfactory.
