This article explains how flow entitlements work in integrator.io — what counts toward your limit, how to monitor usage, and how to optimize if you are approaching your cap.
Note
Usage data — including current and historical usage — is available on the 2024 Platform license only. If you're on the 2022 Endpoint license, usage data is not stored or displayed in integrator.io. To discuss upgrading your license, contact Celigo Support.
A flow in the Celigo platform (integrator.io) represents an automated process or workflow that connects different applications, systems, or data sources to synchronize or move data between them. For example, you could have a flow that syncs customer data from a CRM tool such as Salesforce to an ERP tool such as NetSuite for maintaining up-to-date records.
Flows can vary in complexity, from simple data migrations to multistep processes with conditional logic.
-
Simple flows: Flows that involves basic synchronization or data movement between two applications.
-
Complex flows: Flows that may involve multiple steps, branches, or advanced conditions, consuming more computational resources.
-
Multi-instance flows: A base flow, either simple or complex, from which multiple flow instances are created.
-
Instances: An instance of a base flow, either simple or complex, that runs as a flow.
Based on the limit set under your Celigo platform subscription plan, your account is allowed a certain number of integration flow entitlements in an environment.
Flows run
Distinct integration flows or flow instances that are run, count towards your entitlements in an environment, whether custom-developed or prebuilt, installed from a template, downloaded, or cloned, real-time or scheduled.
The count of flows run is done every month, and you will be notified if you exceed entitlements. If the same flows are run more than once in a month, it does not increase your entitlement.
The following flow types each have specific counting behavior:
-
Custom flows: Custom flows that you build on your own from scratch based on your requirements are counted against your entitlements.
Example 1.
Say, you have two custom flows that you've built in your integration, one that's run in the production environment (Flow A) and another that you're that still building and testing (Flow B).
Flow entitlement count: 1 – Only Flow A that was run
-
Custom flows using a template: Custom flows built using templates, which are available in the Celigo Marketplace free of cost for a quick start, are counted against your entitlements.
Example 2.
Say, you have downloaded and installed the HubSpot – Snowflake Reverse ETL Template with two flows; however, you've only customized and run the Snowflake to HubSpot contact update flow that you require.
Flow entitlement count: 1 – Only the Snowflake to HubSpot contact update flow that was run
-
Multi-instance flows: A custom flow that's used as a base flow from which your instances are created. Any base flow and instances are counted against your entitlements.
Example 3.
Say, you have one custom base flow, and 14 enabled instances running in the production environment. Additionally, you have 5 disabled instances.
Flow entitlement count: 14 – The running instances all count towards your entitlements
-
Integration app flows (prebuilt/managed flows): All distinct Integration app flows that are run are counted against your entitlements.
Note
However, if you're on the legacy endpoint pricing model, then all flows in an Integration app are included in the app's subscription and therefore do not count against your account entitlements, even though flows' connections appear in the endpoint apps total.
Example 4.
Say, you're using the Amazon Seller Central – NetSuite Integration App with 12 available flows; however, based on your requirements, you've only run the following flows:
-
Sync Orders from Amazon to NetSuite
-
Sync Fulfillments from NetSuite to Amazon
-
Sync Item Inventory from NetSuite to Amazon
-
Sync Item Pricing from NetSuite to Amazon
-
Sync Order Cancellations from Amazon to NetSuite
-
Sync Settlement Reports from Amazon to NetSuite
-
Sync Payments from Amazon to NetSuite
-
Sync Refunds from Amazon to NetSuite
Flow entitlement count: 8 – Only the above app flows that were run, not all the app flows
-
-
Exception – Data loader flows: Data loader flows are unlimited and do not apply toward your entitlements. These flows are an exception to the general guideline that allflows run are counted against your entitlements.
Example 5.
If your account has a flow that was run in which you used the data loader to export customer files and then move it to NetSuite. This data loader flow that was run will not be counted against your entitlements.
Flow entitlement count: 0
An account owner or administrator can view a running total of these entitlements and the maximum values allowed in the account Subscription tab.
Administrator
If you're an administrator, you have visibility to all flows run in your account. In the upper right of the Home page, select My account > Subscription.
Note
Usage data — including current and historical usage — is available on the 2024 Platform license only. If you're on the 2022 Endpoint license, usage data is not stored or displayed in integrator.io. To discuss upgrading your license, contact Celigo Support.
Next to Flows run, select View to see detailed usage data for your account.
Users
If you're a user, you have visibility to all flows in integrations or standalone flows (that is, not attached to an integration), select Home > Dashboard and select the Completed flows tab to view the flows that have been run in your account.
Tip
If your license expires and there's a delay in renewal, your integration flows might get automatically disabled. To avoid this, we encourage you to renew your license in time.
To make the most of your entitlements, spend a little time in reviewing the flows run and if you notice that you're exceeding your limit, then you can do either of the following:
-
Upgrade to a higher plan if you notice a pattern that shows where you're running more flows than you're entitled to.
-
If you have overages, you will receive a notification but the flows will not be disrupted and can continue to run. However, it's recommended that you monitor your flows and consider whether there's a consistent pattern of overuse. In this case, perhaps, you can assign a priority to flows so that you can decide if you want to run low-priority flows, or use any other approach to manage your flows within the limits.
|
1. |
Do cloned flows count towards my entitlements? |
|
Yes. While cloned flows are copies of existing flows, they are considered towards your entitlements if they have been run. |
|
|
2. |
Are multi-environment flow entitlements counted separately? |
|
Yes. Distinct flows run are counted separately for multiple environments. For example, consider a case where you have 12 flows run in production and 6 flows run in your sandbox, and you're entitled to run 10 flows each in sandbox and production, that is, a total of 20 flows run. In this case, you can run 12 flows in your production, but the 2 extra flows cannot be offset against the available 4 flows to be run in your sandbox. Legacy production and sandbox licensesIn legacy Production and Sandbox environments, changes in one environment affect both environments. The Production and Sandbox environments share the same underlying resources. Any resource you create, edit, or delete in one environment is immediately reflected in the other. This includes connections, imports, exports, flows, scripts, and API tokens. Use caution when editing resources in either environment. This behavior doesn't apply to accounts on the multi-environment license, where each environment maintains its own isolated resources. Migrations from the legacy Production/Sandbox license to the new multi-environment license are underway. Your account has not migrated to the new multi-environment license if you can toggle between environments. |