Every integration that you create can be defined and measured in terms of tasks. A task, in its most basic forms, is an activity that gets accomplished. An activity can be an action, search, etc. Actions are the events that Integry performs on another app. The number of tasks in an integration depends upon actions, searches and the data that has to be processed to execute it. 

There are different scenarios where we say whether a task is consumed or not. When a task is consumed entirely, it is counted. To know how many tasks your integration consists of, see the examples below. 

Measuring tasks

Integry has defined a task value for each type of step in an integration template. The details on that can be seen below. 

  • Trigger: Unmetered
  • Action: 1 task
  • Conditional Statements: Unmetered
  • Loops: A loop step itself is unmetered. Any activity inside the loop is treated as a separate task and is counted according to its own definition and the number of times it is performed.
  • Error, Failures: 1 task
  • Polling: All polling activities per user are metered for every month. Each poll is considered 1 Task. Minimum poll time is 15min to 5mins depending upon your plan.
  • Schedule Step: Unmetered
  • Setup Step: Unmetered 
  • Storage Step: 1 task. Each storage activity (set value, get value, delete key, etc) performed in the integration counts as 1 task.
  • Loop prevention: If this is toggled on, each individual activity performed until the loop is discontinued, counts as 1 task. It should be noted that when loop prevention is on, certain steps are performed after each trigger receives an event. Those steps as a whole count as one task. So a trigger will comprise of internal steps that will change its task value from unmetered to 1. Details on the extra activities (GET call) can be found here.
    For example, in a 2-way sync integration, if you update a contact in the first app, it will activate the update trigger for that app (1 task). That contact will then be updated with an action step in the second app (1 task). This will activate the update trigger for the second app (1 task) that will check and finally discontinue the loop. So this update of one contact in the 2WS integration will consume 3 tasks in total.
    Using the loop prevention feature is still recommended for 2-way sync templates, as your integrations may face serious issues otherwise. Read all the details of this loop problem here

A few examples below show how tasks are counted in an integration.
Scenario 1

Total integration tasks: The integration above performs 3 tasks. The detailed breakdown of task calculation is as follows:

Once the trigger occurred, Integry performed 3 actions: 1 Action (Add a task in Todoist) + 1 Action (Append a row in GSheets) + 1 Action (Send a message to Convo) = 3 tasks

Conditional Statement Scenario

Total integration tasks: The integration above performs 2 or 3 tasks depending on how it executes as there is a conditional statement. The detailed breakdown of the task calculation is as follows

Case 1: When the if statement is true

Once the trigger occurs, then, 1 Search + 1 Action (Update GSheets) = 2 tasks 

Case 2: When the if statement is false

Once the trigger occurs, then, 1 Search + 1 Action (Add new row in GSheets) + 1 Action (Send a message to Convo) = 3 tasks 

Loops Scenario

The actions inside for loop will be executed multiple times. Hence the number of tasks will be multiplied by the number of items. In the example above, the two actions “Create a Project in Basecamp” and “Post a message to Basecamp” will be multiplied by the number of projects in the Github repository. 

Total integration tasks: Assuming there are 6 projects in the array, the total number of tasks performed by the integration will be 13. The detailed breakdown of task calculation is as follows: 

Once the trigger occurs, then 1 Search + 1 Action (Create a Project in Basecamp)*6 + 1 Action (Post a message to Basecamp)*6  = 13 tasks 

The examples above explain the basic flow of integrations in terms of tasks. We charge you on the basis of usage. Your users are not restricted by the number of tasks allocated to you as per the pricing plan you're on. We will never suspend the service. If your users love the integrations and exceed the allocated task limit, the additional tasks consumed by your customer base will be charged on the prorated charges for additional tasks consumed. 

To learn about our pricing visit our Pricing page

Did this answer your question?